← previous blocknext block →recent activity
Analyzing
Block #96,300,440
6 transactions · 5 stateful · 2026-08-15 20:35:55 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,300,440 · 6 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
1w02w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x99f97262…3ce5
0x34b655…2a6f
4 touches
1 conflict
0xf799bfbd…f710
0x34b655…2a6f
3 touches
1 conflict
0x4cf86968…e398
0x34b655…2a6f
2 touches
0 conflicts
0x4f92c64e…9adc
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 0x31b3992285…921e66
Audit this contract →
← previous block·next block →recent activity