← previous blocknext block →recent activity
Analyzing
Block #109,234,170
11 transactions · 10 stateful · 2026-09-30 05:05:59 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #109,234,170 · 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
6w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe07443e5…c236
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
2 touches
0 conflicts
0x0947f911…896f
0x6f6493…b480
2 touches
0 conflicts
0x0e1f7156…ded1
0x6f6493…b480
2 touches
0 conflicts
0x1d61f2af…7d5e
0x6f6493…b480
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 0xe07443e516…0cc236
Audit this contract →
← previous block·next block →recent activity