← previous blocknext block →recent activity
Analyzing
Block #109,228,224
18 transactions · 12 stateful · 2026-09-30 04:36:04 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,228,224 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w210w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5662cf00…3349
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x90aad2ed…2877
0x34b655…2a6f
4 touches
1 conflict
0x2c5ce8ad…ffd9
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xfd31c2b7…e49f
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x5662cf00b2…4e3349
Audit this contract →
← previous block·next block →recent activity