Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4028519e1d3a75d9dda18e1d22646059272549a7ce3fa801b0b250a3543206e4

Tx prefix hash: d0af6f9da6bee1c394558cc0bd65a82082e7b44ab94c13fa2263cb43ff6baac2
Tx public key: 7f1eb9ca76018d83dad125c94813e418e0d14e35b1332bcae5cd66ee246c2d6d
Timestamp: 1726056221 Timestamp [UCT]: 2024-09-11 12:03:41 Age [y:d:h:m:s]: 00:073:23:07:21
Block: 1107762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52883 RingCT/type: yes/0
Extra: 017f1eb9ca76018d83dad125c94813e418e0d14e35b1332bcae5cd66ee246c2d6d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b548808b0d940dc38efd3434caeb4a2eef708c548e9b19bda8bb49de2110bd90 0.600000000000 1585415 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": 1107772, "vin": [ { "gen": { "height": 1107762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b548808b0d940dc38efd3434caeb4a2eef708c548e9b19bda8bb49de2110bd90" } } ], "extra": [ 1, 127, 30, 185, 202, 118, 1, 141, 131, 218, 209, 37, 201, 72, 19, 228, 24, 224, 209, 78, 53, 177, 51, 43, 202, 229, 205, 102, 238, 36, 108, 45, 109, 2, 17, 0, 0, 0, 9, 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