Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b3a67ba2fba37dcdaec009520f160e1b328566828cc4a0f2d994826fd78b85

Tx prefix hash: 8cc3e65e5a554acd11456f58b11664e89bff90035814f1a327fac6e2f07bcafe
Tx public key: e234c69c15eb788719c7ec6c3d1c6e47d1f5a66d590d39ceefcd07a822817e4a
Timestamp: 1744897406 Timestamp [UCT]: 2025-04-17 13:43:26 Age [y:d:h:m:s]: 00:255:21:34:22
Block: 1263450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180680 RingCT/type: yes/0
Extra: 01e234c69c15eb788719c7ec6c3d1c6e47d1f5a66d590d39ceefcd07a822817e4a021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe219031e286cf1adc68f62300253d6737c2250d3dae963309be8aa25d176d1 0.600000000000 1750641 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": 1263460, "vin": [ { "gen": { "height": 1263450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe219031e286cf1adc68f62300253d6737c2250d3dae963309be8aa25d176d1" } } ], "extra": [ 1, 226, 52, 198, 156, 21, 235, 120, 135, 25, 199, 236, 108, 61, 28, 110, 71, 209, 245, 166, 109, 89, 13, 57, 206, 239, 205, 7, 168, 34, 129, 126, 74, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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