Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428b99b50373c8aef98db34f3cb2fd8290635953fba167224304dc1b4a7f8633

Tx prefix hash: 9296ea7e8be2776510b41d30151d9f8e307a892847871b933282e67718f04ee7
Tx public key: b047b134e8fd67dd4abb66235f8e3bc0171229dbcbb1d9a74e62a472b6deecbf
Timestamp: 1639097566 Timestamp [UCT]: 2021-12-10 00:52:46 Age [y:d:h:m:s]: 03:094:23:59:49
Block: 392141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846634 RingCT/type: yes/0
Extra: 01b047b134e8fd67dd4abb66235f8e3bc0171229dbcbb1d9a74e62a472b6deecbf021100000002379224c2000000000000000000

1 output(s) for total of 30.809815990000 dcy

stealth address amount amount idx
00: 05ff034f55bdf5914cd8844b99205e84808277c82e90d62113b3d7cc8ed9b153 30.809815990000 788900 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": 392151, "vin": [ { "gen": { "height": 392141 } } ], "vout": [ { "amount": 30809815990, "target": { "key": "05ff034f55bdf5914cd8844b99205e84808277c82e90d62113b3d7cc8ed9b153" } } ], "extra": [ 1, 176, 71, 177, 52, 232, 253, 103, 221, 74, 187, 102, 35, 95, 142, 59, 192, 23, 18, 41, 219, 203, 177, 217, 167, 78, 98, 164, 114, 182, 222, 236, 191, 2, 17, 0, 0, 0, 2, 55, 146, 36, 194, 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