Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2334b84cc17926785806ec20a7e8be74039ec5e905f00555de0f5f593b2a375

Tx prefix hash: 95768eb7c6d52a1c949d28e86d7f2adc265914466bbcc3b3bca62c59dcc83814
Tx public key: 566ce05ffad1484e9d1c3011adb0da917340f015b217d67f2fac546f3f2d8d5d
Timestamp: 1734714673 Timestamp [UCT]: 2024-12-20 17:11:13 Age [y:d:h:m:s]: 00:111:15:36:25
Block: 1179453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79571 RingCT/type: yes/0
Extra: 01566ce05ffad1484e9d1c3011adb0da917340f015b217d67f2fac546f3f2d8d5d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c7750951a7d39e180cdacaec99e7eee44a9c2fb47fc28995a1c2460506021b9 0.600000000000 1665848 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": 1179463, "vin": [ { "gen": { "height": 1179453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7750951a7d39e180cdacaec99e7eee44a9c2fb47fc28995a1c2460506021b9" } } ], "extra": [ 1, 86, 108, 224, 95, 250, 209, 72, 78, 157, 28, 48, 17, 173, 176, 218, 145, 115, 64, 240, 21, 178, 23, 214, 127, 47, 172, 84, 111, 63, 45, 141, 93, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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