← previous blocknext block →recent activity
Analyzing
Block #103,221,290
17 transactions · 16 stateful · 2026-09-09 03:45:23 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,221,290 · 17 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
1w02w13w24w15w26w310w412w515w016w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fd951f1…fe49
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xe6d9c62e…465a
0x34b655…2a6f
8 touches
6 conflicts
0x59095657…4424
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x98752ab1…67e2
0x34b655…2a6f
8 touches
6 conflicts
0x1513b999…b52e
0x34b655…2a6f
7 touches
6 conflicts
0x18e881c5…b740
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7fd951f178…5dfe49
Audit this contract →
← previous block·next block →recent activity