Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cea0f67d6299a465674576214f7ca14bf72c46d59d3d6fe70f4a7d13fc223bc3

Tx prefix hash: 8376f84cdabcd2efe29cc3a172663ab0ed5024bc0098e51ce7cd6e79826bcd2d
Tx public key: f2929f9d99babdc56909909634eace717c9a3b4395f935d0fe79b4baa4ea6c1e
Timestamp: 1766219230 Timestamp [UCT]: 2025-12-20 08:27:10 Age [y:d:h:m:s]: 00:016:14:25:26
Block: 1437602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11908 RingCT/type: yes/0
Extra: 01f2929f9d99babdc56909909634eace717c9a3b4395f935d0fe79b4baa4ea6c1e0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d3eb08597b492b14777bcf4410f90bcb928dc60c0cae09bb46763950f843e1 0.600000000000 1926411 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": 1437612, "vin": [ { "gen": { "height": 1437602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d3eb08597b492b14777bcf4410f90bcb928dc60c0cae09bb46763950f843e1" } } ], "extra": [ 1, 242, 146, 159, 157, 153, 186, 189, 197, 105, 9, 144, 150, 52, 234, 206, 113, 124, 154, 59, 67, 149, 249, 53, 208, 254, 121, 180, 186, 164, 234, 108, 30, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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