Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc17961603aca080a1d1a3057a01ac2c75953c140624616654a45baf64e7a104

Tx prefix hash: 41522badb0154d96087c39ad6bf4cdd1d68341040aa37c09dc719499f9912bf1
Tx public key: 80ae02dffee174a7a798ee0fcd36a78d8137e17a83f04028056c0dd5d72ca5e6
Timestamp: 1729429557 Timestamp [UCT]: 2024-10-20 13:05:57 Age [y:d:h:m:s]: 00:240:20:16:01
Block: 1135718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171846 RingCT/type: yes/0
Extra: 0180ae02dffee174a7a798ee0fcd36a78d8137e17a83f04028056c0dd5d72ca5e60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31b9928f6a387010c252d330d5fdf2186c0e9c02b351628244752e88200aa5a5 0.600000000000 1619057 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": 1135728, "vin": [ { "gen": { "height": 1135718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b9928f6a387010c252d330d5fdf2186c0e9c02b351628244752e88200aa5a5" } } ], "extra": [ 1, 128, 174, 2, 223, 254, 225, 116, 167, 167, 152, 238, 15, 205, 54, 167, 141, 129, 55, 225, 122, 131, 240, 64, 40, 5, 108, 13, 213, 215, 44, 165, 230, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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