← previous blocknext block →recent activity
Analyzing
Block #110,208,198
27 transactions · 24 stateful · 2026-10-03 14:49:00 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,208,198 · 27 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
1w04w08w19w210w215w116w017w118w219w322w225w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ad1c5d1…c029
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x58bce2bb…a259
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xf8857df5…9a36
0x34b655…2a6f
5 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x7a1531cd…7319
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
6 conflicts on slot 0x2ad1c5d1c8…d9c029
Audit this contract →
← previous block·next block →recent activity