← previous blocknext block →recent activity
Analyzing
Block #100,920,363
10 transactions · 10 stateful · 2026-09-01 02:15:37 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,920,363 · 10 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
2w04w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
6 touches
3 conflicts
0x6d1ccb53…6db8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3d4f6dac…78d7
0x34b655…2a6f
4 touches
1 conflict
0x26253352…1a75
0x34b655…2a6f
2 touches
0 conflicts
0x27a60404…0093
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
0x34b655…2a6f
2 touches
0 conflicts
0x7061d006…074d
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
3 conflicts on slot 0x831f75b4aa…17945d
Audit this contract →
← previous block·next block →recent activity