Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c409027e868a08d1b2dccb7bd95840863f9493b4adaf3c243c096f70a573192b

Tx prefix hash: 91a70b2234ac13051dbdb213bb32bde86e9cf3b63869225774d34106d0980b1b
Tx public key: 5e6ff44f67b00600e85ba98e844d7a1b6fef5ae61d24144a2f47cee6cac00af9
Timestamp: 1761394071 Timestamp [UCT]: 2025-10-25 12:07:51 Age [y:d:h:m:s]: 00:075:07:56:00
Block: 1397626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53937 RingCT/type: yes/0
Extra: 015e6ff44f67b00600e85ba98e844d7a1b6fef5ae61d24144a2f47cee6cac00af9021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f7cc30ea6df4eb9995ba0fc7a198fc1c579b427665f23db198c317859f305c 0.600000000000 1885917 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": 1397636, "vin": [ { "gen": { "height": 1397626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f7cc30ea6df4eb9995ba0fc7a198fc1c579b427665f23db198c317859f305c" } } ], "extra": [ 1, 94, 111, 244, 79, 103, 176, 6, 0, 232, 91, 169, 142, 132, 77, 122, 27, 111, 239, 90, 230, 29, 36, 20, 74, 47, 71, 206, 230, 202, 192, 10, 249, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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