Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f7e89de9dca9d38ea343b627b54cf3138e955da687e8de939d0be18d42f5e6

Tx prefix hash: beadbd77396e099438c6a9565d02962fbe63a00e3144ee84d54cae91ac512d0d
Tx public key: 6201509e7d9873791694252c7356707c91059fa68a8a89b502c9968f2f5d18f6
Timestamp: 1713055747 Timestamp [UCT]: 2024-04-14 00:49:07 Age [y:d:h:m:s]: 00:214:09:20:41
Block: 999960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153499 RingCT/type: yes/0
Extra: 016201509e7d9873791694252c7356707c91059fa68a8a89b502c9968f2f5d18f602110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c6447f03b483faadaed4d518274ddeaa9fbff2e6a1b4c28252c099ff1718f6 0.600000000000 1460448 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": 999970, "vin": [ { "gen": { "height": 999960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c6447f03b483faadaed4d518274ddeaa9fbff2e6a1b4c28252c099ff1718f6" } } ], "extra": [ 1, 98, 1, 80, 158, 125, 152, 115, 121, 22, 148, 37, 44, 115, 86, 112, 124, 145, 5, 159, 166, 138, 138, 137, 181, 2, 201, 150, 143, 47, 93, 24, 246, 2, 17, 0, 0, 0, 9, 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