Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1aab0e558e2274f8e048d968b317d0cd447fa65b0e3804ac412a59bbac84b18

Tx prefix hash: 32393bf4f9272adab6033b75709305335a4b31fd26a8cb4f3c3257b0cfcf6c4d
Tx public key: 7010a6b84bd1eed53708e575aa53f47f5567a6e57ba2fa54ae50141c46bb1bfa
Timestamp: 1724359879 Timestamp [UCT]: 2024-08-22 20:51:19 Age [y:d:h:m:s]: 00:217:11:42:36
Block: 1093713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155283 RingCT/type: yes/0
Extra: 017010a6b84bd1eed53708e575aa53f47f5567a6e57ba2fa54ae50141c46bb1bfa021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e32009192c427a7d99bed536600cefe6cd3073d18a082d9abf8c5844216b318 0.600000000000 1568710 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": 1093723, "vin": [ { "gen": { "height": 1093713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e32009192c427a7d99bed536600cefe6cd3073d18a082d9abf8c5844216b318" } } ], "extra": [ 1, 112, 16, 166, 184, 75, 209, 238, 213, 55, 8, 229, 117, 170, 83, 244, 127, 85, 103, 166, 229, 123, 162, 250, 84, 174, 80, 20, 28, 70, 187, 27, 250, 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