Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418ff4d5a5348604d4efd9cb87a45bb5810966824f4f85bb8994d980e1e9e458

Tx prefix hash: 030d8f64526e6c4efaa8239eb8eba3acfb9aaff0d12a0c1d4392a2b4b50a20e3
Tx public key: 988e7f5694ce4a147319de1c5438b0df5538e79a7baa41da8ecdd587f94e8d07
Timestamp: 1583988920 Timestamp [UCT]: 2020-03-12 04:55:20 Age [y:d:h:m:s]: 04:326:18:01:24
Block: 80897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128476 RingCT/type: yes/0
Extra: 01988e7f5694ce4a147319de1c5438b0df5538e79a7baa41da8ecdd587f94e8d070211000000024ac5aa02000000000000000000

1 output(s) for total of 331.102862454000 dcy

stealth address amount amount idx
00: 325db1b39bdcae7c517d213598cf9b3c3bfeff708b7e784d66f53bddac77911a 331.102862454000 147989 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": 80907, "vin": [ { "gen": { "height": 80897 } } ], "vout": [ { "amount": 331102862454, "target": { "key": "325db1b39bdcae7c517d213598cf9b3c3bfeff708b7e784d66f53bddac77911a" } } ], "extra": [ 1, 152, 142, 127, 86, 148, 206, 74, 20, 115, 25, 222, 28, 84, 56, 176, 223, 85, 56, 231, 154, 123, 170, 65, 218, 142, 205, 213, 135, 249, 78, 141, 7, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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