← previous blocknext block →recent activity
Analyzing
Block #101,989,959
22 transactions · 20 stateful · 2026-09-04 20:01:00 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,989,959 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w311w113w414w517w419w620w721w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x73ae20cb…19f1
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0x492dfcee…984c
0x34b655…2a6f
4 touches
1 conflict
0x4fa7d903…8b74
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity