← previous blocknext block →recent activity
Analyzing
Block #109,169,620
27 transactions · 19 stateful · 2026-09-29 23:41:06 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,169,620 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w110w020w221w322w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x336486a4…20bd
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
10 touches
10 conflicts
0x6cd112f6…1db7
0x34b655…2a6f
8 touches
6 conflicts
0xe09e568f…0535
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004b
0x80c745…7210
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity