Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc942f892fa649b951d9ed6a566530fb171827edd9c8408aadb6c6776d4a2a67

Tx prefix hash: 52c00a100f7dbd0929173ffc9b4d11bd9db22b423f13dc56fa0d3e95e3e8b140
Tx public key: 4a411df49f3ba23abe18bd64be1fb7cbea36e6344d278db70f896d36c6468d68
Timestamp: 1751466542 Timestamp [UCT]: 2025-07-02 14:29:02 Age [y:d:h:m:s]: 00:134:19:47:17
Block: 1317282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94598 RingCT/type: yes/0
Extra: 014a411df49f3ba23abe18bd64be1fb7cbea36e6344d278db70f896d36c6468d680211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538c5d9acb4f83c3e69c7c99481dda2b27014271ec35821da53bf6f24e2de651 0.600000000000 1804949 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": 1317292, "vin": [ { "gen": { "height": 1317282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538c5d9acb4f83c3e69c7c99481dda2b27014271ec35821da53bf6f24e2de651" } } ], "extra": [ 1, 74, 65, 29, 244, 159, 59, 162, 58, 190, 24, 189, 100, 190, 31, 183, 203, 234, 54, 230, 52, 77, 39, 141, 183, 15, 137, 109, 54, 198, 70, 141, 104, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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