Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b262afe0f7a609cf43c94cf7507496c5cb80cff5b7a01a916218c90fa02e5c5a

Tx prefix hash: cf70b6593e6d733ce8abdb61152cf83add965ebf2a63a73da61a71d3e5a3af84
Tx public key: f49b57cf3f7c586fdcce357974e9766169fb1a74a28b8288c524253e23727d5e
Timestamp: 1752639588 Timestamp [UCT]: 2025-07-16 04:19:48 Age [y:d:h:m:s]: 00:119:04:52:26
Block: 1326471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83938 RingCT/type: yes/0
Extra: 01f49b57cf3f7c586fdcce357974e9766169fb1a74a28b8288c524253e23727d5e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e199b5a1fe44982e406975231a50624da064a01bd9920da8398e3c828ac74be 0.600000000000 1814222 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": 1326481, "vin": [ { "gen": { "height": 1326471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e199b5a1fe44982e406975231a50624da064a01bd9920da8398e3c828ac74be" } } ], "extra": [ 1, 244, 155, 87, 207, 63, 124, 88, 111, 220, 206, 53, 121, 116, 233, 118, 97, 105, 251, 26, 116, 162, 139, 130, 136, 197, 36, 37, 62, 35, 114, 125, 94, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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