Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3411145bc49f28797ccee11c3a9989874a3b1f58ea969241619f3d1aab42d5a5

Tx prefix hash: 269be852d05d89217dfcae48f42cdd7dfb9bcccf593637bde7df0a35a896965c
Tx public key: 2984e0cbb755e740b71937506d192baa108bce9de8c2b8ed15c7b7c01ba38f83
Timestamp: 1706404429 Timestamp [UCT]: 2024-01-28 01:13:49 Age [y:d:h:m:s]: 00:330:18:49:27
Block: 944822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236889 RingCT/type: yes/0
Extra: 012984e0cbb755e740b71937506d192baa108bce9de8c2b8ed15c7b7c01ba38f8302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee0aaaa1b831c48b0960275cc336d7049758302cfa3ea89ad22390909828629e 0.600000000000 1403108 of 15

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": 944832, "vin": [ { "gen": { "height": 944822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee0aaaa1b831c48b0960275cc336d7049758302cfa3ea89ad22390909828629e" } } ], "extra": [ 1, 41, 132, 224, 203, 183, 85, 231, 64, 183, 25, 55, 80, 109, 25, 43, 170, 16, 139, 206, 157, 232, 194, 184, 237, 21, 199, 183, 192, 27, 163, 143, 131, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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