Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7b636d13ce64f61df2ca94018a18a2fa839f7901ed0fb039f5c64d7addda2e

Tx prefix hash: e6dad52cdc6738e1e542a354ef6149a214ae8ee62bcc25adde0c8082e336d141
Tx public key: f0f1f5b14f2d3dc750e866a9d06bebdc20f7cda662dfddb28404d5f4752aa088
Timestamp: 1727188891 Timestamp [UCT]: 2024-09-24 14:41:31 Age [y:d:h:m:s]: 00:218:17:03:30
Block: 1117159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156125 RingCT/type: yes/0
Extra: 01f0f1f5b14f2d3dc750e866a9d06bebdc20f7cda662dfddb28404d5f4752aa088021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c46fd4cdd32851a36858a4de0005667c388b9dfb97563bcba686cc8fd78d384 0.600000000000 1597894 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": 1117169, "vin": [ { "gen": { "height": 1117159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c46fd4cdd32851a36858a4de0005667c388b9dfb97563bcba686cc8fd78d384" } } ], "extra": [ 1, 240, 241, 245, 177, 79, 45, 61, 199, 80, 232, 102, 169, 208, 107, 235, 220, 32, 247, 205, 166, 98, 223, 221, 178, 132, 4, 213, 244, 117, 42, 160, 136, 2, 17, 0, 0, 0, 6, 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