← previous blocknext block →recent activity
Analyzing
Block #109,134,309
15 transactions · 9 stateful · 2026-09-29 20:43:00 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,134,309 · 15 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
6w07w19w213w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe569004f…0228
0x34b655…2a6f
6 touches
3 conflicts
0xfd3d8226…d730
0x34b655…2a6f
4 touches
1 conflict
0x742e5c25…a6b2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc2a722dc…1ef8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0xe569004f07…1d0228
Audit this contract →
← previous block·next block →recent activity