Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee32c29a9d319a102f85de6735c9e323b6230d73c279ed2b3038bdd926961839

Tx prefix hash: 38a0977387f2ac3a280186526317f2a13f9417a43281ec6a3eaf4bf112e0018a
Tx public key: 1f449f3cde493b6c572c8d15358f580d536fe40cdddc67941ee57035b3a49ed7
Timestamp: 1697154018 Timestamp [UCT]: 2023-10-12 23:40:18 Age [y:d:h:m:s]: 01:237:04:40:49
Block: 868351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430598 RingCT/type: yes/0
Extra: 011f449f3cde493b6c572c8d15358f580d536fe40cdddc67941ee57035b3a49ed702110000000633af99f4000000000000000000

1 output(s) for total of 0.814315492000 dcy

stealth address amount amount idx
00: c6c2f9f80f1e87e47b09416d06f23b1583fbdf278b09d42f06247c1f61094ba8 0.814315492000 1323156 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": 868361, "vin": [ { "gen": { "height": 868351 } } ], "vout": [ { "amount": 814315492, "target": { "key": "c6c2f9f80f1e87e47b09416d06f23b1583fbdf278b09d42f06247c1f61094ba8" } } ], "extra": [ 1, 31, 68, 159, 60, 222, 73, 59, 108, 87, 44, 141, 21, 53, 143, 88, 13, 83, 111, 228, 12, 221, 220, 103, 148, 30, 229, 112, 53, 179, 164, 158, 215, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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