← previous blocknext block →recent activity
Analyzing
Block #106,100,787
24 transactions · 22 stateful · 2026-09-19 06:04:17 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,100,787 · 24 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
1w02w03w04w06w110w211w312w413w515w617w618w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
14 touches
21 conflicts
0x382713e8…4417
0x34b655…2a6f
12 touches
15 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
10 touches
10 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x63fba213…5ce2
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
21 conflicts on slot 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity