Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee42b237dcac2199fd773bfc6776fe0e03b581693be4a0da573e0e56bb5290dc

Tx prefix hash: 7ca64f77657a4faaffead261542de42d14aa4c982978f3377251001fb335dddd
Tx public key: 9c5f59e924abc5c5d45c8ed8f47a5f17fe30d123754be97c7d56f1c9138c1baa
Timestamp: 1753874750 Timestamp [UCT]: 2025-07-30 11:25:50 Age [y:d:h:m:s]: 00:119:02:58:27
Block: 1336614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83977 RingCT/type: yes/0
Extra: 019c5f59e924abc5c5d45c8ed8f47a5f17fe30d123754be97c7d56f1c9138c1baa02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cced375ac3b69434de32f4b1260c85e8a82f351663053cdbcd533bbc216ce6c3 0.600000000000 1824415 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": 1336624, "vin": [ { "gen": { "height": 1336614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cced375ac3b69434de32f4b1260c85e8a82f351663053cdbcd533bbc216ce6c3" } } ], "extra": [ 1, 156, 95, 89, 233, 36, 171, 197, 197, 212, 92, 142, 216, 244, 122, 95, 23, 254, 48, 209, 35, 117, 75, 233, 124, 125, 86, 241, 201, 19, 140, 27, 170, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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