← previous blocknext block →recent activity
Analyzing
Block #103,212,103
20 transactions · 19 stateful · 2026-09-09 02:59:06 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,212,103 · 20 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
1w02w13w24w35w47w010w411w513w114w215w318w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0x03f08d80…0661
0x34b655…2a6f
10 touches
10 conflicts
0x18cf84a6…09e4
0x34b655…2a6f
10 touches
10 conflicts
0x2f17174f…68b4
0x34b655…2a6f
10 touches
10 conflicts
0x6dc1811e…2588
0x34b655…2a6f
10 touches
10 conflicts
0x79ec4509…1f61
0x34b655…2a6f
10 touches
10 conflicts
0x87b41dd5…b410
0x34b655…2a6f
10 touches
10 conflicts
0x8b02c6c4…4011
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity