← previous blocknext block →recent activity
Analyzing
Block #96,294,116
8 transactions · 6 stateful · 2026-08-15 20:04:06 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,294,116 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x1a8edc5d…deac
0x0a4fcb…a602
2 touches
0 conflicts
0xc2575a0e…f882
0x0a4fcb…a602
2 touches
0 conflicts
0x2b936aa5…05e5
0x141b1d…9583
2 touches
0 conflicts
0xd37a784f…be3c
0x2185cd…21c7
2 touches
0 conflicts
0x15fa01ab…9ed8
0x34b655…2a6f
2 touches
0 conflicts
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 0x5adda4a7f8…0cb840
Audit this contract →
← previous block·next block →recent activity