Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e49352dc60c54437d63d6e2a4b2d4a268ea68d53661d47a357c73701cee98ce0

Tx prefix hash: 9f188cd240af0f7a6578c569629478a5827fb42a781f65abb33286889475b54e
Tx public key: bd48474bcd97f702366f7a0e90c6b575d9c992c7255a0fa58f1d5378f5aaaa8d
Timestamp: 1734541246 Timestamp [UCT]: 2024-12-18 17:00:46 Age [y:d:h:m:s]: 00:181:08:05:23
Block: 1178029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129284 RingCT/type: yes/0
Extra: 01bd48474bcd97f702366f7a0e90c6b575d9c992c7255a0fa58f1d5378f5aaaa8d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d15984471274f94e37dab85cede45a4d97aa199f7e2a83e95f606b675a66835 0.600000000000 1664412 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": 1178039, "vin": [ { "gen": { "height": 1178029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d15984471274f94e37dab85cede45a4d97aa199f7e2a83e95f606b675a66835" } } ], "extra": [ 1, 189, 72, 71, 75, 205, 151, 247, 2, 54, 111, 122, 14, 144, 198, 181, 117, 217, 201, 146, 199, 37, 90, 15, 165, 143, 29, 83, 120, 245, 170, 170, 141, 2, 17, 0, 0, 0, 1, 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