Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c092aacf8cc6666c105a1a610712eb44bd6aefdf474676d8a37b3ea17868bf

Tx prefix hash: fb458ac2b6ad2bc9df41f55c6e3e8532dd24075249c85fbf086e1cb1de01eb57
Tx public key: 9dbe90d118d6ce5c142956a794a4539f82337b5f6f8bf9ba3e4ba608d16ffae6
Timestamp: 1744686635 Timestamp [UCT]: 2025-04-15 03:10:35 Age [y:d:h:m:s]: 00:290:16:40:03
Block: 1261708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205405 RingCT/type: yes/0
Extra: 019dbe90d118d6ce5c142956a794a4539f82337b5f6f8bf9ba3e4ba608d16ffae6021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2b13d8c6939883e92b1ac1b71c36597906ec52518980ecc2a247189180b9d70 0.600000000000 1748881 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": 1261718, "vin": [ { "gen": { "height": 1261708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2b13d8c6939883e92b1ac1b71c36597906ec52518980ecc2a247189180b9d70" } } ], "extra": [ 1, 157, 190, 144, 209, 24, 214, 206, 92, 20, 41, 86, 167, 148, 164, 83, 159, 130, 51, 123, 95, 111, 139, 249, 186, 62, 75, 166, 8, 209, 111, 250, 230, 2, 17, 0, 0, 0, 3, 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