Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf77f99133ba8e0a1f7c82f4fd0829ed77c823dd841af75b0bc7bb686c5733f5

Tx prefix hash: 66b2b21cedc029b85201a1630651c70984ae5d77d14689c65e04e9a593a0e391
Tx public key: b63408900290ededd01edcb7e12929d81849a3bf18f29bfc0c4b68b020b51b9f
Timestamp: 1578672430 Timestamp [UCT]: 2020-01-10 16:07:10 Age [y:d:h:m:s]: 05:295:14:50:43
Block: 42827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358938 RingCT/type: yes/0
Extra: 01b63408900290ededd01edcb7e12929d81849a3bf18f29bfc0c4b68b020b51b9f0211000000198a2ee0d9000000000000000000

1 output(s) for total of 442.687454146000 dcy

stealth address amount amount idx
00: bce467901bd5b211e4be0775e254aff46035007fe53054eb45595d7019a2ff83 442.687454146000 77275 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": 42837, "vin": [ { "gen": { "height": 42827 } } ], "vout": [ { "amount": 442687454146, "target": { "key": "bce467901bd5b211e4be0775e254aff46035007fe53054eb45595d7019a2ff83" } } ], "extra": [ 1, 182, 52, 8, 144, 2, 144, 237, 237, 208, 30, 220, 183, 225, 41, 41, 216, 24, 73, 163, 191, 24, 242, 155, 252, 12, 75, 104, 176, 32, 181, 27, 159, 2, 17, 0, 0, 0, 25, 138, 46, 224, 217, 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