Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b739e36e4a418774bf18c0fb644107331d269e50f4fc8f971932444c56b17c7

Tx prefix hash: 757de12279657e60a401ec3503aa0f2971c2f7e1423981f76a94d20ecb4b5682
Tx public key: 125e2e3d931c992d9bd4cddd3c3a7ade94d4df0f7a66ddaca3239a8f1e85b18a
Timestamp: 1737671963 Timestamp [UCT]: 2025-01-23 22:39:23 Age [y:d:h:m:s]: 00:140:12:57:56
Block: 1203863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100249 RingCT/type: yes/0
Extra: 01125e2e3d931c992d9bd4cddd3c3a7ade94d4df0f7a66ddaca3239a8f1e85b18a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 466c1cd12ab3b64ca28c072f966fc1abf9c2112ff02611b76bb929c1cc1ae04c 0.600000000000 1690542 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": 1203873, "vin": [ { "gen": { "height": 1203863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "466c1cd12ab3b64ca28c072f966fc1abf9c2112ff02611b76bb929c1cc1ae04c" } } ], "extra": [ 1, 18, 94, 46, 61, 147, 28, 153, 45, 155, 212, 205, 221, 60, 58, 122, 222, 148, 212, 223, 15, 122, 102, 221, 172, 163, 35, 154, 143, 30, 133, 177, 138, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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