Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c5dcc58d577666b1863358576e2814b9c67618127c43378fa19994b32ee1b3

Tx prefix hash: aa36ad5c259188ab2ffd0c7a4711669a1d432a82f71f9e3613a6e8919f294dd8
Tx public key: 8be6ad9ad07235839e9729f2ec1d29309a8a320414ecfdc71391d0c37c405bec
Timestamp: 1724592975 Timestamp [UCT]: 2024-08-25 13:36:15 Age [y:d:h:m:s]: 00:091:11:59:57
Block: 1095626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65446 RingCT/type: yes/0
Extra: 018be6ad9ad07235839e9729f2ec1d29309a8a320414ecfdc71391d0c37c405bec02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f99b01e39a1f2b7874af71f73bc6151eec78c354fea973c1d3ba98c12685b99 0.600000000000 1570807 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": 1095636, "vin": [ { "gen": { "height": 1095626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f99b01e39a1f2b7874af71f73bc6151eec78c354fea973c1d3ba98c12685b99" } } ], "extra": [ 1, 139, 230, 173, 154, 208, 114, 53, 131, 158, 151, 41, 242, 236, 29, 41, 48, 154, 138, 50, 4, 20, 236, 253, 199, 19, 145, 208, 195, 124, 64, 91, 236, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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