Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f058147f48664a3094db9b5de0cd36677e17c9e8e95f05bafe0e60ffdf2251c

Tx prefix hash: 9f250d80b5913b05054bfe9cf9d5a0beac56be2f3f9934d0ceaee39d0a8eac4e
Tx public key: 0f0d8cfcf52040913b1ff3e0a751cb3aa4f37eb39afd3fe31b90f68d00271737
Timestamp: 1736291510 Timestamp [UCT]: 2025-01-07 23:11:50 Age [y:d:h:m:s]: 00:158:06:34:17
Block: 1192480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112853 RingCT/type: yes/0
Extra: 010f0d8cfcf52040913b1ff3e0a751cb3aa4f37eb39afd3fe31b90f68d00271737021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 646306bc45e5d8f114d9c95d1e9f40203b318e2c87c1d2462caf90aac47a55f5 0.600000000000 1679033 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": 1192490, "vin": [ { "gen": { "height": 1192480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646306bc45e5d8f114d9c95d1e9f40203b318e2c87c1d2462caf90aac47a55f5" } } ], "extra": [ 1, 15, 13, 140, 252, 245, 32, 64, 145, 59, 31, 243, 224, 167, 81, 203, 58, 164, 243, 126, 179, 154, 253, 63, 227, 27, 144, 246, 141, 0, 39, 23, 55, 2, 17, 0, 0, 0, 9, 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