Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41bbc7b6dbca8658e5c62794412bd76fa894b924202514f40b0d275922383c11

Tx prefix hash: 8691c9814a8d30ec1183f5696f5495ab7346ab47f09e66032da1119efd68dacf
Tx public key: 3fed7b65ae6fdc847f9c022a6c76256c1f889dbd6c5026e00d32fab93d4450c7
Timestamp: 1728393226 Timestamp [UCT]: 2024-10-08 13:13:46 Age [y:d:h:m:s]: 01:036:10:44:29
Block: 1127144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284433 RingCT/type: yes/0
Extra: 013fed7b65ae6fdc847f9c022a6c76256c1f889dbd6c5026e00d32fab93d4450c7021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68b15aabded6a2d143cc202004212e30f3bcad74d569e345aaedf9ff8a438a1b 0.600000000000 1609943 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": 1127154, "vin": [ { "gen": { "height": 1127144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68b15aabded6a2d143cc202004212e30f3bcad74d569e345aaedf9ff8a438a1b" } } ], "extra": [ 1, 63, 237, 123, 101, 174, 111, 220, 132, 127, 156, 2, 42, 108, 118, 37, 108, 31, 136, 157, 189, 108, 80, 38, 224, 13, 50, 250, 185, 61, 68, 80, 199, 2, 17, 0, 0, 0, 8, 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