← previous blocknext block →recent activity
Analyzing
Block #109,234,018
22 transactions · 21 stateful · 2026-09-30 05:05:13 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,234,018 · 22 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
1w02w13w25w26w08w310w411w512w613w715w316w418w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xf98360fe…0e37
0xd32edf…ff58
9 touches
10 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
6 touches
3 conflicts
0x6235638c…6439
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
4 touches
1 conflict
0x46b08bae…0822
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity