Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 643a11e1485c05558dcaf0ab6a3ad1a878e5e3e88065c4af3e4e2de06f29b1ea

Tx prefix hash: c755b9661a3ea1c6d87864301092ae16d4146c909dfe546fbe743095ae0aca0d
Tx public key: 51472372851d98711e7fef54d8d21d9c066630b586c2173541f8f381c0eac9f6
Timestamp: 1741469467 Timestamp [UCT]: 2025-03-08 21:31:07 Age [y:d:h:m:s]: 00:325:19:15:56
Block: 1235088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230504 RingCT/type: yes/0
Extra: 0151472372851d98711e7fef54d8d21d9c066630b586c2173541f8f381c0eac9f60211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5464039643d4f3bec451cc91d9a19d312d10b9f2893f99cebc855686172d3a2 0.600000000000 1722025 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": 1235098, "vin": [ { "gen": { "height": 1235088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5464039643d4f3bec451cc91d9a19d312d10b9f2893f99cebc855686172d3a2" } } ], "extra": [ 1, 81, 71, 35, 114, 133, 29, 152, 113, 30, 127, 239, 84, 216, 210, 29, 156, 6, 102, 48, 181, 134, 194, 23, 53, 65, 248, 243, 129, 192, 234, 201, 246, 2, 17, 0, 0, 0, 9, 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