Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0807ee47b58ad4d7f95d8169ea1df5d0c3fb5f276d8a1fee4cca3796140b65

Tx prefix hash: 0707cf9b7eb1c0f5d240e9dfb0c3b5fe5f59b7ead512e48aa7433b99d2ba4d4a
Tx public key: 496dadfaf9922fdbfb4b913e5b066a2d34c3d6c58272828023829b110070385a
Timestamp: 1728171690 Timestamp [UCT]: 2024-10-05 23:41:30 Age [y:d:h:m:s]: 00:206:10:43:21
Block: 1125304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 147386 RingCT/type: yes/0
Extra: 01496dadfaf9922fdbfb4b913e5b066a2d34c3d6c58272828023829b110070385a

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a27031c82ae9f83033233fd3be751eb1e59127f24887bef802749b2ed81bcbf 0.600000000000 1607985 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": 1125314, "vin": [ { "gen": { "height": 1125304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a27031c82ae9f83033233fd3be751eb1e59127f24887bef802749b2ed81bcbf" } } ], "extra": [ 1, 73, 109, 173, 250, 249, 146, 47, 219, 251, 75, 145, 62, 91, 6, 106, 45, 52, 195, 214, 197, 130, 114, 130, 128, 35, 130, 155, 17, 0, 112, 56, 90 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8