Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b58a4996ac9fdefb0cf6234005ce4073d68889fb6e617d9712b2dbf0a28446

Tx prefix hash: 5dffb4862262d4bd8ffa748b5eefd81b79cd2ca84dcfb7ea7f42a504521e1a95
Tx public key: 8597de8fba8b6c59aff17e6040b66a263170e51e51c3baa64f3a5649513c76ce
Timestamp: 1742971278 Timestamp [UCT]: 2025-03-26 06:41:18 Age [y:d:h:m:s]: 00:240:16:48:55
Block: 1247503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169777 RingCT/type: yes/0
Extra: 018597de8fba8b6c59aff17e6040b66a263170e51e51c3baa64f3a5649513c76ce021100000003165b77a1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da3a14a19a2c5a30aa37e375c8de867950e3aa00113f0e0fd004986a729d0b36 0.600000000000 1734522 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": 1247513, "vin": [ { "gen": { "height": 1247503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da3a14a19a2c5a30aa37e375c8de867950e3aa00113f0e0fd004986a729d0b36" } } ], "extra": [ 1, 133, 151, 222, 143, 186, 139, 108, 89, 175, 241, 126, 96, 64, 182, 106, 38, 49, 112, 229, 30, 81, 195, 186, 166, 79, 58, 86, 73, 81, 60, 118, 206, 2, 17, 0, 0, 0, 3, 22, 91, 119, 161, 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