Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcc4c0fa3c0770b4dd907cea18c7f6162fad11c6a139d9c7f49071a33cee5328

Tx prefix hash: b2940da0a87f37ef29d9189014c9cd2081a61cc17259e502659c45e99d44083e
Tx public key: 1e594714b2bbedce94a94a44c919b354e4cbadb662ab4665b19342042c12d844
Timestamp: 1703971719 Timestamp [UCT]: 2023-12-30 21:28:39 Age [y:d:h:m:s]: 01:169:09:48:52
Block: 924663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382132 RingCT/type: yes/0
Extra: 011e594714b2bbedce94a94a44c919b354e4cbadb662ab4665b19342042c12d84402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a649086c8ee14f7e5a1b3f47e299d9a2d397170a432c2c8ca0698c4b1e8b120 0.600000000000 1382419 of 15

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": 924673, "vin": [ { "gen": { "height": 924663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a649086c8ee14f7e5a1b3f47e299d9a2d397170a432c2c8ca0698c4b1e8b120" } } ], "extra": [ 1, 30, 89, 71, 20, 178, 187, 237, 206, 148, 169, 74, 68, 201, 25, 179, 84, 228, 203, 173, 182, 98, 171, 70, 101, 177, 147, 66, 4, 44, 18, 216, 68, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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