Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a13d27b399dc7f86e36b9ac8da78d6b60126609c80f451e2f99261564decbbcd

Tx prefix hash: 0de552789942a96af0ac6128a2cb680e32eba06400fceb898bc09f97eac10823
Tx public key: 6a9b852855f5bae2417652810477bfdd51b0e97b89b9fee4c9e0cb4823b1bf5f
Timestamp: 1745957133 Timestamp [UCT]: 2025-04-29 20:05:33 Age [y:d:h:m:s]: 00:205:19:49:17
Block: 1272234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144808 RingCT/type: yes/0
Extra: 016a9b852855f5bae2417652810477bfdd51b0e97b89b9fee4c9e0cb4823b1bf5f0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be8221708c62e03c7d7f84fdcc0db283c8e0fa0031cb2adf6d3164eca26fa745 0.600000000000 1759507 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": 1272244, "vin": [ { "gen": { "height": 1272234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be8221708c62e03c7d7f84fdcc0db283c8e0fa0031cb2adf6d3164eca26fa745" } } ], "extra": [ 1, 106, 155, 133, 40, 85, 245, 186, 226, 65, 118, 82, 129, 4, 119, 191, 221, 81, 176, 233, 123, 137, 185, 254, 228, 201, 224, 203, 72, 35, 177, 191, 95, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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