Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c32b22aa6243c9e9485dff9c230e7657d95b07db2f3f88305f4f4ea49375e60

Tx prefix hash: 2829d16f9bec43240571b93b41d6a5a9730a0bc8383a2f6ad4ca0149cb692913
Tx public key: a23481af7cc4512a238324bf6ae9a88da32de4c7d92ca11dc1a6896d4a867ddb
Timestamp: 1745057885 Timestamp [UCT]: 2025-04-19 10:18:05 Age [y:d:h:m:s]: 00:200:11:26:08
Block: 1264781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140982 RingCT/type: yes/0
Extra: 01a23481af7cc4512a238324bf6ae9a88da32de4c7d92ca11dc1a6896d4a867ddb0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01dce0c47a310e83f747c42a68de9999a7ccf532ede8abce0b9177da6778ba8 0.600000000000 1751982 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": 1264791, "vin": [ { "gen": { "height": 1264781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01dce0c47a310e83f747c42a68de9999a7ccf532ede8abce0b9177da6778ba8" } } ], "extra": [ 1, 162, 52, 129, 175, 124, 196, 81, 42, 35, 131, 36, 191, 106, 233, 168, 141, 163, 45, 228, 199, 217, 44, 161, 29, 193, 166, 137, 109, 74, 134, 125, 219, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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