← previous blocknext block →recent activity
Analyzing
Block #110,392,391
16 transactions · 14 stateful · 2026-10-04 06:15:48 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,392,391 · 16 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
1w05w19w010w111w213w014w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe693687c…56d4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0x31cf1c6c…57c3
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0xaa43b9ee…b72e
0x34b655…2a6f
4 touches
1 conflict
0xb13b96bd…a3cb
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
3 conflicts on slot 0xe693687c16…c556d4
Audit this contract →
← previous block·next block →recent activity