Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdebaecbac103869b2c2eeebc273c016ac6ec98574e1238d7a513855a441a6ec

Tx prefix hash: c50ad19dde0504d7bd902ba286b47282c94ae851afc3d2c69d50d1259ac00402
Tx public key: 2c8cb42e6a5360bfd5da0fbd17c7d73106f3a5e2a145729f977294902f97e7a5
Timestamp: 1743746232 Timestamp [UCT]: 2025-04-04 05:57:12 Age [y:d:h:m:s]: 00:022:13:20:32
Block: 1253930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16142 RingCT/type: yes/0
Extra: 012c8cb42e6a5360bfd5da0fbd17c7d73106f3a5e2a145729f977294902f97e7a502110000000aa2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 100f945abfefa57076c082ce0532e29e7495a64ff9e235d35e262b4ec379a2eb 0.600000000000 1741011 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": 1253940, "vin": [ { "gen": { "height": 1253930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "100f945abfefa57076c082ce0532e29e7495a64ff9e235d35e262b4ec379a2eb" } } ], "extra": [ 1, 44, 140, 180, 46, 106, 83, 96, 191, 213, 218, 15, 189, 23, 199, 215, 49, 6, 243, 165, 226, 161, 69, 114, 159, 151, 114, 148, 144, 47, 151, 231, 165, 2, 17, 0, 0, 0, 10, 162, 237, 1, 107, 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