← previous blocknext block →recent activity
Analyzing
Block #101,681,747
9 transactions · 9 stateful · 2026-09-03 18:06:33 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,681,747 · 9 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
2w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee0c2fbd…fd33
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x15073066…40a5
0x34b655…2a6f
2 touches
0 conflicts
0x1df07d43…ff95
0x34b655…2a6f
2 touches
0 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
2 touches
0 conflicts
0x2f5c6ab7…20ab
0x34b655…2a6f
2 touches
0 conflicts
0x39561c15…c70f
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 0xee0c2fbde9…66fd33
Audit this contract →
← previous block·next block →recent activity