Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cec3c06189ed5009c2661ae9d3662badf9ef64738b3bcef20e5be8ac344863e

Tx prefix hash: 2ca5d9a0fc8bde38212dd7945da826c1bce19aee9a292efb99f0e89989b2a149
Tx public key: 3817a93609128615d5b5536e533bab4612d8d896a4132515f5df6b30237e85a4
Timestamp: 1708611803 Timestamp [UCT]: 2024-02-22 14:23:23 Age [y:d:h:m:s]: 01:047:22:22:55
Block: 963143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295279 RingCT/type: yes/0
Extra: 013817a93609128615d5b5536e533bab4612d8d896a4132515f5df6b30237e85a40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 569fb41b255a434dad8b905f236ed2d7640ef6323f21fe15c59d0282e4678f19 0.600000000000 1422842 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": 963153, "vin": [ { "gen": { "height": 963143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "569fb41b255a434dad8b905f236ed2d7640ef6323f21fe15c59d0282e4678f19" } } ], "extra": [ 1, 56, 23, 169, 54, 9, 18, 134, 21, 213, 181, 83, 110, 83, 59, 171, 70, 18, 216, 216, 150, 164, 19, 37, 21, 245, 223, 107, 48, 35, 126, 133, 164, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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