← previous blocknext block →recent activity
Analyzing
Block #96,604,813
8 transactions · 6 stateful · 2026-08-16 22:07:04 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,604,813 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79adeae4…34ff
0x34b655…2a6f
4 touches
1 conflict
0x34724223…fd0f
0x34b655…2a6f
4 touches
1 conflict
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0x00d2ebd1…2c24
0x34b655…2a6f
2 touches
0 conflicts
0x258e45aa…333e
0x34b655…2a6f
2 touches
0 conflicts
0x2d651956…12e8
0x34b655…2a6f
2 touches
0 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
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 0x79adeae4ce…9d34ff
Audit this contract →
← previous block·next block →recent activity