← previous blocknext block →recent activity
Analyzing
Block #110,379,650
33 transactions · 28 stateful · 2026-10-04 05:11:42 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,379,650 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w08w09w112w113w219w121w223w024w026w027w130w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x12530975…a089
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x453805…c7fd
6 touches
3 conflicts
0x00000000…0002
0x453805…c7fd
6 touches
3 conflicts
0x00000000…0004
0x453805…c7fd
6 touches
3 conflicts
0x00000000…000c
0x453805…c7fd
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 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
3 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity