Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f5ae15a1a4eb7efbd93b036d5d11487c040f88ae83671fb3993f351acf1588

Tx prefix hash: 714ba3858441e6897a3cb1bbd3ffa07a688a0092a0a267e69963b98ab90da16a
Tx public key: 886c021eb3743565a84edf5a1efd78f178384713bda26fac71dc77b2384a624f
Timestamp: 1693082314 Timestamp [UCT]: 2023-08-26 20:38:34 Age [y:d:h:m:s]: 01:137:12:33:25
Block: 834560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359652 RingCT/type: yes/0
Extra: 01886c021eb3743565a84edf5a1efd78f178384713bda26fac71dc77b2384a624f0211000000024b8f5122000000000000000000

1 output(s) for total of 1.053795542000 dcy

stealth address amount amount idx
00: 0d8f8386f5d01ae767afe6122aa0d457b6ac0d361b76221136d61aac2ce99029 1.053795542000 1287058 of 0

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": 834570, "vin": [ { "gen": { "height": 834560 } } ], "vout": [ { "amount": 1053795542, "target": { "key": "0d8f8386f5d01ae767afe6122aa0d457b6ac0d361b76221136d61aac2ce99029" } } ], "extra": [ 1, 136, 108, 2, 30, 179, 116, 53, 101, 168, 78, 223, 90, 30, 253, 120, 241, 120, 56, 71, 19, 189, 162, 111, 172, 113, 220, 119, 178, 56, 74, 98, 79, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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