Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1154e2db8e083af08a1d861c130df5350d0cfaf6c2c2c789f730c2be72ea666d

Tx prefix hash: 569dc306431ccc50f399e809b4a6ff09c0a7664a37d15b8ad3e17f0bc454c8c4
Tx public key: f7a20441e173c56de546b22b8174afbf7d30b59d48bd8f8ab69288e9c34cc671
Timestamp: 1752520307 Timestamp [UCT]: 2025-07-14 19:11:47 Age [y:d:h:m:s]: 00:173:00:47:00
Block: 1325509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122473 RingCT/type: yes/0
Extra: 01f7a20441e173c56de546b22b8174afbf7d30b59d48bd8f8ab69288e9c34cc67102110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eaa8442254f76717e8ff1568c7e1ed76e71d834e2a20c6f4954e16ec4ab2e86 0.600000000000 1813254 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": 1325519, "vin": [ { "gen": { "height": 1325509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eaa8442254f76717e8ff1568c7e1ed76e71d834e2a20c6f4954e16ec4ab2e86" } } ], "extra": [ 1, 247, 162, 4, 65, 225, 115, 197, 109, 229, 70, 178, 43, 129, 116, 175, 191, 125, 48, 181, 157, 72, 189, 143, 138, 182, 146, 136, 233, 195, 76, 198, 113, 2, 17, 0, 0, 0, 2, 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