Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e03ccb582b18057872d806ac49c7338d972af59997f7015cf5540c8f78ca434

Tx prefix hash: 39a455d655f5a3d8739d514f516064613d1bc0e9f9a10ad1226e1bb826c42457
Tx public key: 00c1ba875315236323a71dce803d3c40691d68f71c907902c080ab9f7e2b99e5
Timestamp: 1717711892 Timestamp [UCT]: 2024-06-06 22:11:32 Age [y:d:h:m:s]: 00:232:01:24:25
Block: 1038587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166023 RingCT/type: yes/0
Extra: 0100c1ba875315236323a71dce803d3c40691d68f71c907902c080ab9f7e2b99e502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a4df71db72b2d5790d1c084e7a29e079b62606650fb6ce0e8c4c13201491bb 0.600000000000 1507148 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": 1038597, "vin": [ { "gen": { "height": 1038587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a4df71db72b2d5790d1c084e7a29e079b62606650fb6ce0e8c4c13201491bb" } } ], "extra": [ 1, 0, 193, 186, 135, 83, 21, 35, 99, 35, 167, 29, 206, 128, 61, 60, 64, 105, 29, 104, 247, 28, 144, 121, 2, 192, 128, 171, 159, 126, 43, 153, 229, 2, 17, 0, 0, 0, 1, 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