Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7896f73900f99932b26c3e1f1c1f8812f21f693b2be848567bf203782958b5

Tx prefix hash: 90c4f10c79444f2c17f44fec5073c072ae43e0be0f429b68d804b3a536161309
Tx public key: 9e966cc05d33bca53addf2d0a8ebf7b70fb3316a7926588395173a432a55c7a8
Timestamp: 1711560624 Timestamp [UCT]: 2024-03-27 17:30:24 Age [y:d:h:m:s]: 01:007:08:12:06
Block: 987606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266188 RingCT/type: yes/0
Extra: 019e966cc05d33bca53addf2d0a8ebf7b70fb3316a7926588395173a432a55c7a802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 973000fb963931752b2d3f7db1aec12cfe3cd17d2b0017c69e4c17de1e5ba2e6 0.600000000000 1447859 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": 987616, "vin": [ { "gen": { "height": 987606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "973000fb963931752b2d3f7db1aec12cfe3cd17d2b0017c69e4c17de1e5ba2e6" } } ], "extra": [ 1, 158, 150, 108, 192, 93, 51, 188, 165, 58, 221, 242, 208, 168, 235, 247, 183, 15, 179, 49, 106, 121, 38, 88, 131, 149, 23, 58, 67, 42, 85, 199, 168, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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