Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394e8bae35a39e2612d00c24d6328f388b7d7ce61e26359fe804e676a0233497

Tx prefix hash: 4239df17afb597f878d8b08f875a1326e88d2c4d360d69ab915f9dfdeb777f6f
Tx public key: ef863dbd38a9b20ad8c86716ba0f176a9065fa142d6f780dd7ec22723e609d0a
Timestamp: 1669723367 Timestamp [UCT]: 2022-11-29 12:02:47 Age [y:d:h:m:s]: 02:132:10:22:07
Block: 641647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 616341 RingCT/type: yes/0
Extra: 01ef863dbd38a9b20ad8c86716ba0f176a9065fa142d6f780dd7ec22723e609d0a02110000000afaf35c9c000000000000000000

1 output(s) for total of 4.591526841000 dcy

stealth address amount amount idx
00: 2b849378a5d47d6a208e8e3c6cb9c912a8a0e603ddd006c5e7e6eda7ec056760 4.591526841000 1081462 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": 641657, "vin": [ { "gen": { "height": 641647 } } ], "vout": [ { "amount": 4591526841, "target": { "key": "2b849378a5d47d6a208e8e3c6cb9c912a8a0e603ddd006c5e7e6eda7ec056760" } } ], "extra": [ 1, 239, 134, 61, 189, 56, 169, 178, 10, 216, 200, 103, 22, 186, 15, 23, 106, 144, 101, 250, 20, 45, 111, 120, 13, 215, 236, 34, 114, 62, 96, 157, 10, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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