Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffda6a223346f3760367cb955bed412ff70b402be113274f23627e7c6c664d82

Tx prefix hash: e288d5a8fe624a8e6039bef89d9724b5044adbd2057fc1b591a0c5a6970aa24c
Tx public key: 20b63e3332ea570a615edc297f95a293e4bdbf824a14a0bf41d243a2653cdcb2
Timestamp: 1709133803 Timestamp [UCT]: 2024-02-28 15:23:23 Age [y:d:h:m:s]: 01:091:13:46:57
Block: 967478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326495 RingCT/type: yes/0
Extra: 0120b63e3332ea570a615edc297f95a293e4bdbf824a14a0bf41d243a2653cdcb20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1202636ef6973c45775446ea32ebef55ae0c041bc5d9908c393eff383d4c15f 0.600000000000 1427257 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": 967488, "vin": [ { "gen": { "height": 967478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1202636ef6973c45775446ea32ebef55ae0c041bc5d9908c393eff383d4c15f" } } ], "extra": [ 1, 32, 182, 62, 51, 50, 234, 87, 10, 97, 94, 220, 41, 127, 149, 162, 147, 228, 189, 191, 130, 74, 20, 160, 191, 65, 210, 67, 162, 101, 60, 220, 178, 2, 17, 0, 0, 0, 1, 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