← previous blocknext block →recent activity
Analyzing
Block #106,187,995
26 transactions · 26 stateful · 2026-09-19 13:23:10 UTC
Parallelism
81/100
Blocked
62%
Avg conflicts / tx
1.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,187,995 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w08w110w212w213w214w315w416w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xb935707a…140f
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x6ab4583b…79db
0x34b655…2a6f
8 touches
6 conflicts
0x581b829b…9578
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity