Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfba992f5730c2ab4c65fe696384724bff04aaf086a91634c8180c028f0d54fc

Tx prefix hash: 29ed64002d94cddb07fda66125c3b139bf343d8f8a492d51714252724a03a300
Tx public key: 8ba7cd652a936e12d6e34f8969b6f8f1b5f17807c22a42dd2a9b4128ca6d7b1d
Timestamp: 1696470621 Timestamp [UCT]: 2023-10-05 01:50:21 Age [y:d:h:m:s]: 01:194:20:29:50
Block: 862684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400315 RingCT/type: yes/0
Extra: 018ba7cd652a936e12d6e34f8969b6f8f1b5f17807c22a42dd2a9b4128ca6d7b1d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.850295399000 dcy

stealth address amount amount idx
00: 624aef8dda8aa3df5907d59c15631eb3ea1bcbdb1ed35f9ad83ae7d5594bfec9 0.850295399000 1317116 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": 862694, "vin": [ { "gen": { "height": 862684 } } ], "vout": [ { "amount": 850295399, "target": { "key": "624aef8dda8aa3df5907d59c15631eb3ea1bcbdb1ed35f9ad83ae7d5594bfec9" } } ], "extra": [ 1, 139, 167, 205, 101, 42, 147, 110, 18, 214, 227, 79, 137, 105, 182, 248, 241, 181, 241, 120, 7, 194, 42, 66, 221, 42, 155, 65, 40, 202, 109, 123, 29, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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