Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5004fb99b9997a97c6edbbda16508b0e8b9493b682b8195f0844b43e9951a5

Tx prefix hash: f9b4a94f0504c06dbac5f82148d15fcde2007af8ac6e2319af30d39564c4158a
Tx public key: f0fc6b78ad168b5afe222619441b1dc1dfbe845e67536ce991b39df570aa5c1e
Timestamp: 1753030693 Timestamp [UCT]: 2025-07-20 16:58:13 Age [y:d:h:m:s]: 00:123:06:19:59
Block: 1329657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86899 RingCT/type: yes/0
Extra: 01f0fc6b78ad168b5afe222619441b1dc1dfbe845e67536ce991b39df570aa5c1e02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49ce5fa2d43ddb2ec971bc646d1120067d75cccaf7d2568711f36fd323716fb9 0.600000000000 1817446 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": 1329667, "vin": [ { "gen": { "height": 1329657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49ce5fa2d43ddb2ec971bc646d1120067d75cccaf7d2568711f36fd323716fb9" } } ], "extra": [ 1, 240, 252, 107, 120, 173, 22, 139, 90, 254, 34, 38, 25, 68, 27, 29, 193, 223, 190, 132, 94, 103, 83, 108, 233, 145, 179, 157, 245, 112, 170, 92, 30, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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