← previous blocknext block →recent activity
Analyzing
Block #109,234,428
23 transactions · 20 stateful · 2026-09-30 05:07:17 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,234,428 · 23 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
1w02w03w05w16w18w19w110w111w212w314w420w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8313d5c…8ef5
0x34b655…2a6f
8 touches
6 conflicts
0x2f8d5499…f5a4
0x34b655…2a6f
8 touches
6 conflicts
0xf35dca9e…bd8b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x07b3b023…1780
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x339de58f…2eaf
0xd32edf…ff58
5 touches
3 conflicts
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 0xb8313d5c48…658ef5
Audit this contract →
← previous block·next block →recent activity