Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf497747cdaae79d9fcb03fae8de3c51a7fade50c3b0d0ab1975982ff6418dc

Tx prefix hash: 9f0a6589475ae2c7ae1b01419eb17adcd1f82ebb47d4fe48f59ab8a1793a648d
Tx public key: 9b58997d19b74623d276bf0147c315f222ef4052b823e8b0791b38165af4aef1
Timestamp: 1720138548 Timestamp [UCT]: 2024-07-05 00:15:48 Age [y:d:h:m:s]: 00:284:10:34:49
Block: 1058699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203241 RingCT/type: yes/0
Extra: 019b58997d19b74623d276bf0147c315f222ef4052b823e8b0791b38165af4aef10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34831392a2e24991ad65fd7cc19dd5c6577eb7ba27cb495c5b6ba12caaefbc5e 0.600000000000 1529156 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": 1058709, "vin": [ { "gen": { "height": 1058699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34831392a2e24991ad65fd7cc19dd5c6577eb7ba27cb495c5b6ba12caaefbc5e" } } ], "extra": [ 1, 155, 88, 153, 125, 25, 183, 70, 35, 210, 118, 191, 1, 71, 195, 21, 242, 34, 239, 64, 82, 184, 35, 232, 176, 121, 27, 56, 22, 90, 244, 174, 241, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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