Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a4c3db069ecdf1675f9266244938ee3e1f235bf28e28ee8c8040867cd2ab3e7

Tx prefix hash: a0fa26ae5717de2f264a211f747c5d9d3c0202d946548b9c1285e12ef44489f4
Tx public key: 2b171ea543936b3baeff442b093f953ee0fd23d293aa964758cf1942ad3a65a4
Timestamp: 1708927457 Timestamp [UCT]: 2024-02-26 06:04:17 Age [y:d:h:m:s]: 01:043:02:20:56
Block: 965762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291818 RingCT/type: yes/0
Extra: 012b171ea543936b3baeff442b093f953ee0fd23d293aa964758cf1942ad3a65a402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05d83b23b43aa6b39da5eba929b3485489f489eec38f16ddb5a2cf0fd53c131 0.600000000000 1425517 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": 965772, "vin": [ { "gen": { "height": 965762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05d83b23b43aa6b39da5eba929b3485489f489eec38f16ddb5a2cf0fd53c131" } } ], "extra": [ 1, 43, 23, 30, 165, 67, 147, 107, 59, 174, 255, 68, 43, 9, 63, 149, 62, 224, 253, 35, 210, 147, 170, 150, 71, 88, 207, 25, 66, 173, 58, 101, 164, 2, 17, 0, 0, 0, 6, 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