Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db20a5abb1cf8198dfe937aebb1bf3f6b96c95d36c0ce4b3b0d009a6ad182909

Tx prefix hash: 91c07ea8e0a5ae84540963a8d35b872a26b4c1be35cd613f6c5963c81aa9910d
Tx public key: ef200ee323173ab3884194cba96b1ec42c1979c0b6bb7221be06881f61dcbdd5
Timestamp: 1761651590 Timestamp [UCT]: 2025-10-28 11:39:50 Age [y:d:h:m:s]: 00:072:12:17:04
Block: 1399758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51915 RingCT/type: yes/0
Extra: 01ef200ee323173ab3884194cba96b1ec42c1979c0b6bb7221be06881f61dcbdd502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9d40d14042918b9536ef1a6a556e1e2dc12a93970a3094fb05d4edb15acfad1 0.600000000000 1888063 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": 1399768, "vin": [ { "gen": { "height": 1399758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d40d14042918b9536ef1a6a556e1e2dc12a93970a3094fb05d4edb15acfad1" } } ], "extra": [ 1, 239, 32, 14, 227, 35, 23, 58, 179, 136, 65, 148, 203, 169, 107, 30, 196, 44, 25, 121, 192, 182, 187, 114, 33, 190, 6, 136, 31, 97, 220, 189, 213, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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