Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a743f1243cca445d12579089946df8624ac498d0e9e26717a71e2c1b4abe9d

Tx prefix hash: 04c566f8e8b8fabda7fe160aa93823a37e0a3a595939fe97c9fc852fe84c73a1
Tx public key: b6c7987133b85d7b0db9ba8121177c48e5e1b220e29e617523d3ca8e88b9f084
Timestamp: 1707770313 Timestamp [UCT]: 2024-02-12 20:38:33 Age [y:d:h:m:s]: 01:295:06:09:28
Block: 956158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469814 RingCT/type: yes/0
Extra: 01b6c7987133b85d7b0db9ba8121177c48e5e1b220e29e617523d3ca8e88b9f084021100000001b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdc3b4aebbc53340382aa1d590b46864632cd2eb8ba54ae4739f976db1d8a2c4 0.600000000000 1415460 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": 956168, "vin": [ { "gen": { "height": 956158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdc3b4aebbc53340382aa1d590b46864632cd2eb8ba54ae4739f976db1d8a2c4" } } ], "extra": [ 1, 182, 199, 152, 113, 51, 184, 93, 123, 13, 185, 186, 129, 33, 23, 124, 72, 229, 225, 178, 32, 226, 158, 97, 117, 35, 211, 202, 142, 136, 185, 240, 132, 2, 17, 0, 0, 0, 1, 182, 226, 220, 51, 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