Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e7005c84e3ddfa673ba7b667ca2ea7c61c7612e6a0b1367b7bf5e95058ed52

Tx prefix hash: 5035a3c216185a63b34c377caf53d196e18bb1adf866e973089337908c8bcc24
Tx public key: 1cdb1e1b3a510b9a8c00dd44872401fd11eb7eb2c1c3cd626580030542413cbb
Timestamp: 1759699634 Timestamp [UCT]: 2025-10-05 21:27:14 Age [y:d:h:m:s]: 00:095:07:43:04
Block: 1383564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68261 RingCT/type: yes/0
Extra: 011cdb1e1b3a510b9a8c00dd44872401fd11eb7eb2c1c3cd626580030542413cbb021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c07ba525cbe2641bb8eacff985d345419a6b0b91d44d91d766cc1d0581b370f 0.600000000000 1871711 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": 1383574, "vin": [ { "gen": { "height": 1383564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c07ba525cbe2641bb8eacff985d345419a6b0b91d44d91d766cc1d0581b370f" } } ], "extra": [ 1, 28, 219, 30, 27, 58, 81, 11, 154, 140, 0, 221, 68, 135, 36, 1, 253, 17, 235, 126, 178, 193, 195, 205, 98, 101, 128, 3, 5, 66, 65, 60, 187, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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