← previous blocknext block →recent activity
Analyzing
Block #96,372,016
13 transactions · 13 stateful · 2026-08-16 02:35:55 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,372,016 · 13 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
1w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7feb1ae…2a5a
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0x242bdfb5…974d
0x34b655…2a6f
2 touches
0 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdd1
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7213
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 0xd7feb1ae0a…5a2a5a
Audit this contract →
← previous block·next block →recent activity