Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a9423e0407a803ad33772040b6792ea4b8bc1b3f04b76ef4852797214e0f6db

Tx prefix hash: 62ea9a035aeabaf0cce4eb9aa3f77e3917e1607dd9e6e211dd15278ff2b44e34
Tx public key: a56e9a5e01d0e424e969a07e375cec3c9d23e909f384658cbbbc743bce344a86
Timestamp: 1701766722 Timestamp [UCT]: 2023-12-05 08:58:42 Age [y:d:h:m:s]: 01:193:13:59:00
Block: 906387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399450 RingCT/type: yes/0
Extra: 01a56e9a5e01d0e424e969a07e375cec3c9d23e909f384658cbbbc743bce344a8602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.609205175000 dcy

stealth address amount amount idx
00: 979aa10be330793b019c066d9fb4fb19eb7c32778757f0c3e30e7a93b7917ca2 0.609205175000 1363318 of 0

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": 906397, "vin": [ { "gen": { "height": 906387 } } ], "vout": [ { "amount": 609205175, "target": { "key": "979aa10be330793b019c066d9fb4fb19eb7c32778757f0c3e30e7a93b7917ca2" } } ], "extra": [ 1, 165, 110, 154, 94, 1, 208, 228, 36, 233, 105, 160, 126, 55, 92, 236, 60, 157, 35, 233, 9, 243, 132, 101, 140, 187, 188, 116, 59, 206, 52, 74, 134, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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