Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c3d629cf63303d139731edda683284918c9e618bdd16232aa0c4e76fe70d9b

Tx prefix hash: 45caeb858d4db5e3c9d4ac70ae83215336b85ed1b9bca81036136d91b22ed277
Tx public key: 312129c5f660a4a57b2d43b70c3001e57c736c34b4e6b31078132fa10c11b418
Timestamp: 1752595595 Timestamp [UCT]: 2025-07-15 16:06:35 Age [y:d:h:m:s]: 00:175:20:06:57
Block: 1326117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124490 RingCT/type: yes/0
Extra: 01312129c5f660a4a57b2d43b70c3001e57c736c34b4e6b31078132fa10c11b418021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bbc3c2a44694fd623ef8c72a83099e8365fd1925b13acc869f1569f2b24614f 0.600000000000 1813866 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": 1326127, "vin": [ { "gen": { "height": 1326117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bbc3c2a44694fd623ef8c72a83099e8365fd1925b13acc869f1569f2b24614f" } } ], "extra": [ 1, 49, 33, 41, 197, 246, 96, 164, 165, 123, 45, 67, 183, 12, 48, 1, 229, 124, 115, 108, 52, 180, 230, 179, 16, 120, 19, 47, 161, 12, 17, 180, 24, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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