Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d7b97c782919ee66c8aff51678a1f1cc1f5285a3c522307dbf23c3032c4575

Tx prefix hash: d62abadb4b0cfd235c2e04f702ff21ff45be3d046be9e30c4ef46e12b16de090
Tx public key: 04c0a6baedadc98de80a00a9c9f474d1d9725b2f492ba8a17038d75130c277a1
Timestamp: 1725064067 Timestamp [UCT]: 2024-08-31 00:27:47 Age [y:d:h:m:s]: 00:220:11:35:17
Block: 1099539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157421 RingCT/type: yes/0
Extra: 0104c0a6baedadc98de80a00a9c9f474d1d9725b2f492ba8a17038d75130c277a1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b8a73e208923a7197e6419b2696576750291a0ed63f845e8ce8f71c730b9ea1 0.600000000000 1575502 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": 1099549, "vin": [ { "gen": { "height": 1099539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b8a73e208923a7197e6419b2696576750291a0ed63f845e8ce8f71c730b9ea1" } } ], "extra": [ 1, 4, 192, 166, 186, 237, 173, 201, 141, 232, 10, 0, 169, 201, 244, 116, 209, 217, 114, 91, 47, 73, 43, 168, 161, 112, 56, 215, 81, 48, 194, 119, 161, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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