← previous blocknext block →recent activity
Analyzing
Block #95,406,910
17 transactions · 14 stateful · 2026-08-12 17:39:35 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,406,910 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xe69df7e2…3022
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0xf5547123…bec8
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x1b733940…05ee
0x34b655…2a6f
4 touches
1 conflict
0x1c255c26…11dd
0x34b655…2a6f
4 touches
1 conflict
0x2e8187e0…ffb6
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity