← previous blocknext block →recent activity
Analyzing
Block #96,090,033
8 transactions · 8 stateful · 2026-08-15 02:57:36 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,090,033 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4ee6d8a…dfae
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x12bc05e5…2456
0x34b655…2a6f
2 touches
0 conflicts
0x131a4489…c12c
0x34b655…2a6f
2 touches
0 conflicts
0x182a2a24…e089
0x34b655…2a6f
2 touches
0 conflicts
0x1e1f8d85…2092
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 0xf4ee6d8a5f…83dfae
Audit this contract →
← previous block·next block →recent activity