Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03f5844e56b554efeb8ee5885674d7c66071eca60b9f264f668025722d9f1ce4

Tx prefix hash: 778852f6f55938b6fa07737aca079d956c94adf6de4907affe85e2ed363ce7ae
Tx public key: acaa7b89c0224dc4acf024d38986f783a6ddb4e11d9c61195f77d9ca04dffc5a
Timestamp: 1751835632 Timestamp [UCT]: 2025-07-06 21:00:32 Age [y:d:h:m:s]: 00:135:17:14:19
Block: 1320161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95410 RingCT/type: yes/0
Extra: 01acaa7b89c0224dc4acf024d38986f783a6ddb4e11d9c61195f77d9ca04dffc5a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136e5c4f3034da0f9b9b9cf603cf7e81517c9fca6481d08ba0e3fcc7da547e31 0.600000000000 1807856 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": 1320171, "vin": [ { "gen": { "height": 1320161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136e5c4f3034da0f9b9b9cf603cf7e81517c9fca6481d08ba0e3fcc7da547e31" } } ], "extra": [ 1, 172, 170, 123, 137, 192, 34, 77, 196, 172, 240, 36, 211, 137, 134, 247, 131, 166, 221, 180, 225, 29, 156, 97, 25, 95, 119, 217, 202, 4, 223, 252, 90, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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