← previous blocknext block →recent activity
Analyzing
Block #109,144,713
10 transactions · 10 stateful · 2026-09-29 21:35:46 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,144,713 · 10 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
1w02w15w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9833a2dc…032c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9264281d…c902
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0052
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb2
0x1b6862…e19c
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 0x9833a2dc9a…b4032c
Audit this contract →
← previous block·next block →recent activity