← previous blocknext block →recent activity
Analyzing
Block #101,017,602
28 transactions · 18 stateful · 2026-09-01 10:24:49 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,017,602 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w09w015w116w217w320w421w523w624w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8db32935…81a7
0x34b655…2a6f
14 touches
21 conflicts
0x453f02ab…512d
0x34b655…2a6f
10 touches
10 conflicts
0xc125f6c9…07f6
0x34b655…2a6f
10 touches
10 conflicts
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57cbaf2e…4b8a
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity