← previous blocknext block →recent activity
Analyzing
Block #96,087,903
8 transactions · 8 stateful · 2026-08-15 02:46:53 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,087,903 · 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
1w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x003b6142…6bce
0x34b655…2a6f
2 touches
0 conflicts
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x0649b8e0…c704
0x34b655…2a6f
2 touches
0 conflicts
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x2c2db8e9…fdc7
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity