Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d061fe621612981287438d6da1cc6ca61a8b2667404d80cc749035dfb0efae8a

Tx prefix hash: 2c6530177f42749b50da0af4cd38ceebb9c7486c0433c1a109d2ccfe33ab3dcf
Tx public key: 238f80768afe1edd01a94bde71159cdf893635b6c0df261fa32bdbecee4dd3e5
Timestamp: 1725507613 Timestamp [UCT]: 2024-09-05 03:40:13 Age [y:d:h:m:s]: 01:063:08:05:49
Block: 1103220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303697 RingCT/type: yes/0
Extra: 01238f80768afe1edd01a94bde71159cdf893635b6c0df261fa32bdbecee4dd3e502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 913ec4e6e90a7aec0d25e517c5f88c66a074ebf64e7449e573327975162a6d1e 0.600000000000 1579961 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": 1103230, "vin": [ { "gen": { "height": 1103220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "913ec4e6e90a7aec0d25e517c5f88c66a074ebf64e7449e573327975162a6d1e" } } ], "extra": [ 1, 35, 143, 128, 118, 138, 254, 30, 221, 1, 169, 75, 222, 113, 21, 156, 223, 137, 54, 53, 182, 192, 223, 38, 31, 163, 43, 219, 236, 238, 77, 211, 229, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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