← previous blocknext block →recent activity
Analyzing
Block #106,190,778
11 transactions · 10 stateful · 2026-09-19 13:37:10 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,190,778 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x969f2d28…4fa2
0x0555e3…2b9c
2 touches
0 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
2 touches
0 conflicts
0xc707fd5c…6e1b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity