Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060ebe2202895096c90f9ff14645159bed40b34a75e5008efebc5c8156fefb4e

Tx prefix hash: 536b7b910e5fe15ed9afc9f6368c0160745ef3acb75ee878d7066f25bb78cd07
Tx public key: 257fa30d7e670b2460f10e0d9d6a05cb3a413a5b8cf717b10fbc2f29c634ed52
Timestamp: 1716343859 Timestamp [UCT]: 2024-05-22 02:10:59 Age [y:d:h:m:s]: 00:299:09:06:00
Block: 1027246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213993 RingCT/type: yes/0
Extra: 01257fa30d7e670b2460f10e0d9d6a05cb3a413a5b8cf717b10fbc2f29c634ed5202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8554338c3837b9650d29d7c1fa244ebe442b8b19438f88f93185db88b3b4fd69 0.600000000000 1494765 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": 1027256, "vin": [ { "gen": { "height": 1027246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8554338c3837b9650d29d7c1fa244ebe442b8b19438f88f93185db88b3b4fd69" } } ], "extra": [ 1, 37, 127, 163, 13, 126, 103, 11, 36, 96, 241, 14, 13, 157, 106, 5, 203, 58, 65, 58, 91, 140, 247, 23, 177, 15, 188, 47, 41, 198, 52, 237, 82, 2, 17, 0, 0, 0, 2, 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