Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 728da5369ef4539d457f935d9c521277f2064faad6b081b4468e089749a0a80a

Tx prefix hash: 692d96b26db9e7169ea93e94c9f31a97a1c59840944058cad988543342580252
Tx public key: 47d2edcb72e63407dee027e726ddb4d8d2d9cae743a32af50c7d0196a4699baf
Timestamp: 1721891840 Timestamp [UCT]: 2024-07-25 07:17:20 Age [y:d:h:m:s]: 00:122:15:08:23
Block: 1073232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87750 RingCT/type: yes/0
Extra: 0147d2edcb72e63407dee027e726ddb4d8d2d9cae743a32af50c7d0196a4699baf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08d73eaea85597fecc725ec31cd7917f1771df0061fbcb0c7ca3bd3de2701d10 0.600000000000 1545731 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": 1073242, "vin": [ { "gen": { "height": 1073232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08d73eaea85597fecc725ec31cd7917f1771df0061fbcb0c7ca3bd3de2701d10" } } ], "extra": [ 1, 71, 210, 237, 203, 114, 230, 52, 7, 222, 224, 39, 231, 38, 221, 180, 216, 210, 217, 202, 231, 67, 163, 42, 245, 12, 125, 1, 150, 164, 105, 155, 175, 2, 17, 0, 0, 0, 3, 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