Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d733347228c8c207145f2727a925e0c24ff8782be353cdfe7a761eb565da4631

Tx prefix hash: b7b6a524838673a246e55733f3c20765db661974b8ce052c810d4af3de430317
Tx public key: e12baed4f90d8004c5d5ab8fa3de985ca88a4ce48c511a6a7b85ff12ea27a8d4
Timestamp: 1721398281 Timestamp [UCT]: 2024-07-19 14:11:21 Age [y:d:h:m:s]: 00:269:21:18:07
Block: 1069160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192796 RingCT/type: yes/0
Extra: 01e12baed4f90d8004c5d5ab8fa3de985ca88a4ce48c511a6a7b85ff12ea27a8d4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad7719a9ec6f38262c720757a7ebf41e8afee6aa0c438d8a8c1ceaa59774908d 0.600000000000 1540475 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": 1069170, "vin": [ { "gen": { "height": 1069160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad7719a9ec6f38262c720757a7ebf41e8afee6aa0c438d8a8c1ceaa59774908d" } } ], "extra": [ 1, 225, 43, 174, 212, 249, 13, 128, 4, 197, 213, 171, 143, 163, 222, 152, 92, 168, 138, 76, 228, 140, 81, 26, 106, 123, 133, 255, 18, 234, 39, 168, 212, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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