Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1a8b7d7c75441c448a1fdcdd637e05d6be5b2374332ab1f3831df1fe362b5692

Tx prefix hash: 1a406f6fb42e55ea30c88d309bf4094e00114a2b55d1487c24986d94cd870324
Tx public key: 2166ce26d0e3762cdc79240e6da1c9e5b9cf33c49e107bd191edc7fb31c974f2
Timestamp: 1631500057 Timestamp [UCT]: 2021-09-13 02:27:37 Age [y:d:h:m:s]: 03:111:17:21:47
Block: 332661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855426 RingCT/type: yes/0
Extra: 012166ce26d0e3762cdc79240e6da1c9e5b9cf33c49e107bd191edc7fb31c974f2021100000016f60c5d7e000000000000000000

1 output(s) for total of 48.501643542000 dcy

stealth address amount amount idx
00: ab1f9a1bcac59b83f5ec9748d36f74c16b28f174a289d23c488ff7a523c42a95 48.501643542000 686848 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 332671, "vin": [ { "gen": { "height": 332661 } } ], "vout": [ { "amount": 48501643542, "target": { "key": "ab1f9a1bcac59b83f5ec9748d36f74c16b28f174a289d23c488ff7a523c42a95" } } ], "extra": [ 1, 33, 102, 206, 38, 208, 227, 118, 44, 220, 121, 36, 14, 109, 161, 201, 229, 185, 207, 51, 196, 158, 16, 123, 209, 145, 237, 199, 251, 49, 201, 116, 242, 2, 17, 0, 0, 0, 22, 246, 12, 93, 126, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8