← previous blocknext block →recent activity
Analyzing
Block #110,156,388
18 transactions · 16 stateful · 2026-10-03 10:28:20 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,156,388 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6473d9b1…3273
0x34b655…2a6f
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x1cc97f22…bfd3
0x34b655…2a6f
2 touches
0 conflicts
0x4a4fd881…d274
0x34b655…2a6f
2 touches
0 conflicts
0x50c2d612…2f61
0x34b655…2a6f
2 touches
0 conflicts
0x5a541bec…80fc
0x34b655…2a6f
2 touches
0 conflicts
0x6921ddde…d0d0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6473d9b18e…0e3273
Audit this contract →
← previous block·next block →recent activity