Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2497cd338f2586fe2b3c4c13c80e904df6cf53ac5a71d70ab65ad6234944ef89

Tx prefix hash: 4b784d9ea803913ad8ae2217afae87ae1ed3127e0b8473e2312f4bfe6ee5bb14
Tx public key: 86e8d484dc7a0eb2559d7159e62ebef728abf09f040d00acdcc9f6601d3e3048
Timestamp: 1725857873 Timestamp [UCT]: 2024-09-09 04:57:53 Age [y:d:h:m:s]: 00:261:23:01:44
Block: 1106121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187103 RingCT/type: yes/0
Extra: 0186e8d484dc7a0eb2559d7159e62ebef728abf09f040d00acdcc9f6601d3e304802110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 302dacf68dc63b6af1ff331485ba21028ef366f8fc6f0d38bbf02a6c779ff8f4 0.600000000000 1583702 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": 1106131, "vin": [ { "gen": { "height": 1106121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "302dacf68dc63b6af1ff331485ba21028ef366f8fc6f0d38bbf02a6c779ff8f4" } } ], "extra": [ 1, 134, 232, 212, 132, 220, 122, 14, 178, 85, 157, 113, 89, 230, 46, 190, 247, 40, 171, 240, 159, 4, 13, 0, 172, 220, 201, 246, 96, 29, 62, 48, 72, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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