Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9390691798e2a458a3436030d3a934d8765abb7e897421a6dcbaf5b7232395d8

Tx prefix hash: cda6daf009f63f35b59430e10c3316e4e01db8cd6d0fb5da0a79d1060e79d873
Tx public key: b912ae64a64d2a921268e9453f4966e4c599578c87c332de6e565f0905580f7e
Timestamp: 1720577489 Timestamp [UCT]: 2024-07-10 02:11:29 Age [y:d:h:m:s]: 00:141:10:22:31
Block: 1062349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101207 RingCT/type: yes/0
Extra: 01b912ae64a64d2a921268e9453f4966e4c599578c87c332de6e565f0905580f7e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 954140a4bb11af995dec77addabf98b2c8a9f5cee0256069c5471bc737e93b50 0.600000000000 1532850 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": 1062359, "vin": [ { "gen": { "height": 1062349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "954140a4bb11af995dec77addabf98b2c8a9f5cee0256069c5471bc737e93b50" } } ], "extra": [ 1, 185, 18, 174, 100, 166, 77, 42, 146, 18, 104, 233, 69, 63, 73, 102, 228, 197, 153, 87, 140, 135, 195, 50, 222, 110, 86, 95, 9, 5, 88, 15, 126, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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