← previous blocknext block →recent activity
Analyzing
Block #110,220,435
21 transactions · 19 stateful · 2026-10-03 15:50:38 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,220,435 · 21 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
7w08w110w011w113w014w115w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3d5e890…2dfc
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5bf29e70…4100
0x34b655…2a6f
4 touches
1 conflict
0x6a0203f2…d145
0x34b655…2a6f
4 touches
1 conflict
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xe3d5e890ad…5f2dfc
Audit this contract →
← previous block·next block →recent activity