← previous blocknext block →recent activity
Analyzing
Block #101,896,414
20 transactions · 17 stateful · 2026-09-04 12:06:32 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,896,414 · 20 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
1w02w13w24w35w48w39w010w111w012w113w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xdbf974a4…b232
0x34b655…2a6f
6 touches
3 conflicts
0xdf146090…28f8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x46c14e01…ff09
0x34b655…2a6f
6 touches
3 conflicts
0x59d2df30…aff2
0x34b655…2a6f
5 touches
3 conflicts
0x01315072…0e2d
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
10 conflicts on slot 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity