Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233cef663044b58ea1b4c74a39951bcdc2f62382dcfd2a8b772c65d75130c0b1

Tx prefix hash: 19ddbb769e20d4efefcb601c8743e01c50836ab7ae16884c916fc73a632b1c78
Tx public key: e3f4f7545fb08892b4acb675ba17b90452299ae8e535ca50c3535c29671d6207
Timestamp: 1750990180 Timestamp [UCT]: 2025-06-27 02:09:40 Age [y:d:h:m:s]: 00:147:01:52:27
Block: 1313566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103124 RingCT/type: yes/0
Extra: 01e3f4f7545fb08892b4acb675ba17b90452299ae8e535ca50c3535c29671d6207021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c61076bedb03dd16ff950c02fa41ace9ecc4aa9e153c3407832bbfb82e4c2f10 0.600000000000 1801207 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": 1313576, "vin": [ { "gen": { "height": 1313566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c61076bedb03dd16ff950c02fa41ace9ecc4aa9e153c3407832bbfb82e4c2f10" } } ], "extra": [ 1, 227, 244, 247, 84, 95, 176, 136, 146, 180, 172, 182, 117, 186, 23, 185, 4, 82, 41, 154, 232, 229, 53, 202, 80, 195, 83, 92, 41, 103, 29, 98, 7, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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