Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c6961e16d5a79152b46dd21c49736dcd8c026699e152231e85d42fb9f197821

Tx prefix hash: 45e1bf37c94fca761002478fe2bc5f2099f0390a07ca3980dab3e7917c4ade90
Tx public key: 129bd344801aaef51ae30958f4f89bd5f47aa1d2db68e3ea714f126e6f5b158d
Timestamp: 1731134296 Timestamp [UCT]: 2024-11-09 06:38:16 Age [y:d:h:m:s]: 00:133:02:35:41
Block: 1149782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94957 RingCT/type: yes/0
Extra: 01129bd344801aaef51ae30958f4f89bd5f47aa1d2db68e3ea714f126e6f5b158d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaf812addfba233f06a33c622f0e7fd48986d1c589744309d5360e3bf930f828 0.600000000000 1634943 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": 1149792, "vin": [ { "gen": { "height": 1149782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf812addfba233f06a33c622f0e7fd48986d1c589744309d5360e3bf930f828" } } ], "extra": [ 1, 18, 155, 211, 68, 128, 26, 174, 245, 26, 227, 9, 88, 244, 248, 155, 213, 244, 122, 161, 210, 219, 104, 227, 234, 113, 79, 18, 110, 111, 91, 21, 141, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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