Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e052e124030f67482bb853dc0ffc245f814f09b072ff8f6578943527d613879

Tx prefix hash: a9912d936eb09d84f5cab27bee51cec29c6cfabfd99a8ababdd2fa53655286d5
Tx public key: 1258d5eb681b404e9fe32fbc738fa20d9de7b7ba7d4d606b2a1f787b346077a0
Timestamp: 1727240046 Timestamp [UCT]: 2024-09-25 04:54:06 Age [y:d:h:m:s]: 00:121:14:40:31
Block: 1117578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86909 RingCT/type: yes/0
Extra: 011258d5eb681b404e9fe32fbc738fa20d9de7b7ba7d4d606b2a1f787b346077a0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ce8e3bb20b866637b984af7b90deffd58887fc3b32faec818265f00f8c9f03 0.600000000000 1598467 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": 1117588, "vin": [ { "gen": { "height": 1117578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ce8e3bb20b866637b984af7b90deffd58887fc3b32faec818265f00f8c9f03" } } ], "extra": [ 1, 18, 88, 213, 235, 104, 27, 64, 78, 159, 227, 47, 188, 115, 143, 162, 13, 157, 231, 183, 186, 125, 77, 96, 107, 42, 31, 120, 123, 52, 96, 119, 160, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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