Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e936ccc46f0cc2b9770bc16219d9cd7f74287574682a8c7d317db0c3ba10f12e

Tx prefix hash: 19cba70016937742a324bd1d4c6193c28ad9061e759f8f691049c4b483930562
Tx public key: c7e1e0657c53d336f0f10a1885fdacdecbd5a096e167d9cc9ba7ce4154d80d8c
Timestamp: 1734241666 Timestamp [UCT]: 2024-12-15 05:47:46 Age [y:d:h:m:s]: 00:095:04:34:08
Block: 1175533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67822 RingCT/type: yes/0
Extra: 01c7e1e0657c53d336f0f10a1885fdacdecbd5a096e167d9cc9ba7ce4154d80d8c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39e6c1725ecff48c10515861309a24755abc539ad3eabb7968606b5ebde26ae9 0.600000000000 1661824 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": 1175543, "vin": [ { "gen": { "height": 1175533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39e6c1725ecff48c10515861309a24755abc539ad3eabb7968606b5ebde26ae9" } } ], "extra": [ 1, 199, 225, 224, 101, 124, 83, 211, 54, 240, 241, 10, 24, 133, 253, 172, 222, 203, 213, 160, 150, 225, 103, 217, 204, 155, 167, 206, 65, 84, 216, 13, 140, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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