Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a96d0dcfc0aa5a55f56f7e07686d441851fd0132b99a281c0130531e5035b7c

Tx prefix hash: f4117d130e7cdbb5c23dd562c6cc68585ae5e9914aa1c64c3326ac6ece64f86f
Tx public key: 137f975eb50d05e9e0e7af4abd599cafdf20437248286d5b42868464f8a9fdf7
Timestamp: 1701771114 Timestamp [UCT]: 2023-12-05 10:11:54 Age [y:d:h:m:s]: 01:084:18:00:10
Block: 906422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321693 RingCT/type: yes/0
Extra: 01137f975eb50d05e9e0e7af4abd599cafdf20437248286d5b42868464f8a9fdf702110000000c33af99f4000000000000000000

1 output(s) for total of 0.609042521000 dcy

stealth address amount amount idx
00: 1b4f05b6ffe7805298d7ea7cb3278bff103970406f5aadfc36a04a7dd80f7e0d 0.609042521000 1363355 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": 906432, "vin": [ { "gen": { "height": 906422 } } ], "vout": [ { "amount": 609042521, "target": { "key": "1b4f05b6ffe7805298d7ea7cb3278bff103970406f5aadfc36a04a7dd80f7e0d" } } ], "extra": [ 1, 19, 127, 151, 94, 181, 13, 5, 233, 224, 231, 175, 74, 189, 89, 156, 175, 223, 32, 67, 114, 72, 40, 109, 91, 66, 134, 132, 100, 248, 169, 253, 247, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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