Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 131b8977a94ebdfbb41e323c02862d17dcca12c5bfb5faf4476c8795d1ce4688

Tx prefix hash: 4e5520f39a86f515376c27b21320b8d657eac9ea4d7916f5f2106c12ac4ad758
Tx public key: 0d91a3a8def8420eabfe8c4b2af992135197e64f2c67d66c176fb2ff896fa735
Timestamp: 1697657541 Timestamp [UCT]: 2023-10-18 19:32:21 Age [y:d:h:m:s]: 01:245:18:57:57
Block: 872525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436578 RingCT/type: yes/0
Extra: 010d91a3a8def8420eabfe8c4b2af992135197e64f2c67d66c176fb2ff896fa73502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.788791998000 dcy

stealth address amount amount idx
00: c3b550dca23e21a46d5c0b6cd78d7a9e68c7b1c0d955557f4a84f69afd7051bd 0.788791998000 1327615 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": 872535, "vin": [ { "gen": { "height": 872525 } } ], "vout": [ { "amount": 788791998, "target": { "key": "c3b550dca23e21a46d5c0b6cd78d7a9e68c7b1c0d955557f4a84f69afd7051bd" } } ], "extra": [ 1, 13, 145, 163, 168, 222, 248, 66, 14, 171, 254, 140, 75, 42, 249, 146, 19, 81, 151, 230, 79, 44, 103, 214, 108, 23, 111, 178, 255, 137, 111, 167, 53, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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