← previous blocknext block →recent activity
Analyzing
Block #109,133,396
20 transactions · 16 stateful · 2026-09-29 20:38:25 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,133,396 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w310w011w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb771853a…e31d
0xe1c8b7…3022
4 touches
1 conflict
0xe569004f…0228
0x34b655…2a6f
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x6ac338e8…93bb
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x97199b…5aad
4 touches
1 conflict
0xe2cb724f…81ed
0xd8e004…7777
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity