← previous blocknext block →recent activity
Analyzing
Block #109,004,418
34 transactions · 26 stateful · 2026-09-29 09:47:48 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,004,418 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w117w018w119w220w321w427w028w129w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa12725e0…dede
0x34b655…2a6f
10 touches
10 conflicts
0xb195cffa…8098
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xf353c5ad…c4f0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
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
10 conflicts on slot 0xa12725e0f4…fddede
Audit this contract →
← previous block·next block →recent activity