Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7340a73c6c173d636df409b87777b1e8c6e8434f4f0bd189baa1df75f1ff8f

Tx prefix hash: 8098aa50b9c70828e1579807eba1567e1b39f7987679aea009e9fd44a7fb6644
Tx public key: 8493564b680183ce59b9d3066a150bad61e2533f792fddc69cb875423717331c
Timestamp: 1725808793 Timestamp [UCT]: 2024-09-08 15:19:53 Age [y:d:h:m:s]: 00:121:05:39:26
Block: 1105717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86701 RingCT/type: yes/0
Extra: 018493564b680183ce59b9d3066a150bad61e2533f792fddc69cb875423717331c021100000003e914dd15000000000000000000

1 output(s) for total of 0.608020000000 dcy

stealth address amount amount idx
00: d04aab07ba3ecc46aed2029e0a98e4cf1cba0b5df7a5af0cca1a7a4a3e6a3bec 0.608020000000 1583148 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": 1105727, "vin": [ { "gen": { "height": 1105717 } } ], "vout": [ { "amount": 608020000, "target": { "key": "d04aab07ba3ecc46aed2029e0a98e4cf1cba0b5df7a5af0cca1a7a4a3e6a3bec" } } ], "extra": [ 1, 132, 147, 86, 75, 104, 1, 131, 206, 89, 185, 211, 6, 106, 21, 11, 173, 97, 226, 83, 63, 121, 47, 221, 198, 156, 184, 117, 66, 55, 23, 51, 28, 2, 17, 0, 0, 0, 3, 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