Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1f38580a0e223279f91bf4c281d0cf338be38c73b773a3a3d308b5f17d16c5

Tx prefix hash: 18f724d6e893e3610684af4eca0d515945790931afc5c5135d0304ad245bdc66
Tx public key: e00bb07714b844db6b3495be134175d0437e4c08a2f4e52cd5a4feb9894da5c4
Timestamp: 1703036233 Timestamp [UCT]: 2023-12-20 01:37:13 Age [y:d:h:m:s]: 01:097:10:40:55
Block: 916919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330752 RingCT/type: yes/0
Extra: 01e00bb07714b844db6b3495be134175d0437e4c08a2f4e52cd5a4feb9894da5c4021100000008e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7cfac9069236fb2d8834b0c3addde4306b5d97777662b105c97b8333450691c 0.600000000000 1374481 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": 916929, "vin": [ { "gen": { "height": 916919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7cfac9069236fb2d8834b0c3addde4306b5d97777662b105c97b8333450691c" } } ], "extra": [ 1, 224, 11, 176, 119, 20, 184, 68, 219, 107, 52, 149, 190, 19, 65, 117, 208, 67, 126, 76, 8, 162, 244, 229, 44, 213, 164, 254, 185, 137, 77, 165, 196, 2, 17, 0, 0, 0, 8, 228, 187, 107, 131, 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