Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee10913c47ee88284c6e12427c7676ac4fa82cf213a77e58fe3fd7d1b323bb33

Tx prefix hash: 66486a05de2ae7b00e2062c2e4a263b44292c98e86956af27187872c8414995a
Tx public key: c1707da86b17fdfef77d21f951790eecb215032e3d324bb57896c6d0fa382206
Timestamp: 1751496026 Timestamp [UCT]: 2025-07-02 22:40:26 Age [y:d:h:m:s]: 00:213:13:15:31
Block: 1317519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150788 RingCT/type: yes/0
Extra: 01c1707da86b17fdfef77d21f951790eecb215032e3d324bb57896c6d0fa38220602110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1317ae97aa3bdf9e3b96ec66ea81a17a842e45d7cb3df8ea3ea5b2aca00f6810 0.600000000000 1805188 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": 1317529, "vin": [ { "gen": { "height": 1317519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1317ae97aa3bdf9e3b96ec66ea81a17a842e45d7cb3df8ea3ea5b2aca00f6810" } } ], "extra": [ 1, 193, 112, 125, 168, 107, 23, 253, 254, 247, 125, 33, 249, 81, 121, 14, 236, 178, 21, 3, 46, 61, 50, 75, 181, 120, 150, 198, 208, 250, 56, 34, 6, 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