← previous blocknext block →recent activity
Analyzing
Block #109,144,721
14 transactions · 13 stateful · 2026-09-29 21:35:49 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,144,721 · 14 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
3w04w15w26w37w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4188cc5f…2d2e
0x34b655…2a6f
8 touches
6 conflicts
0xbade0a0a…d5c9
0x34b655…2a6f
8 touches
6 conflicts
0x5a61e295…58c5
0x34b655…2a6f
8 touches
6 conflicts
0x68f7aaba…88df
0x34b655…2a6f
6 touches
3 conflicts
0x9264281d…c902
0x34b655…2a6f
6 touches
3 conflicts
0xbaf77397…e798
0x34b655…2a6f
6 touches
3 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
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
6 conflicts on slot 0x4188cc5f13…782d2e
Audit this contract →
← previous block·next block →recent activity