← previous blocknext block →recent activity
Analyzing
Block #96,372,132
14 transactions · 13 stateful · 2026-08-16 02:36:30 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,372,132 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
6 touches
3 conflicts
0x2f3561fa…8d5d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x701208a7…46b3
0x34b655…2a6f
4 touches
1 conflict
0x75586248…f0b4
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
3 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity