Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f09e933a04018e875f5d6b1130da3c5d716399f8745446aabec01a25170c470

Tx prefix hash: b795b94c6499a702934e1ebb89c8650f2dedd3a30c4e52a7fad2becfa450f532
Tx public key: b084eafee01b29d93c2b00a7e9b4765bdd78f16360d697fb19e504c45081e4ec
Timestamp: 1716295849 Timestamp [UCT]: 2024-05-21 12:50:49 Age [y:d:h:m:s]: 00:155:08:30:36
Block: 1026856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111241 RingCT/type: yes/0
Extra: 01b084eafee01b29d93c2b00a7e9b4765bdd78f16360d697fb19e504c45081e4ec02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ab60aa46c65060933266e4cd408f519ba78f690f1f11e4a0ebb3e2ba450b770 0.600000000000 1494163 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": 1026866, "vin": [ { "gen": { "height": 1026856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ab60aa46c65060933266e4cd408f519ba78f690f1f11e4a0ebb3e2ba450b770" } } ], "extra": [ 1, 176, 132, 234, 254, 224, 27, 41, 217, 60, 43, 0, 167, 233, 180, 118, 91, 221, 120, 241, 99, 96, 214, 151, 251, 25, 229, 4, 196, 80, 129, 228, 236, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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