← previous blocknext block →recent activity
Analyzing
Block #110,135,092
9 transactions · 8 stateful · 2026-10-03 08:41:12 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,135,092 · 9 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
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2b31b795…80a0
0x34b655…2a6f
4 touches
1 conflict
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0x95c486a3…3c2f
0x34b655…2a6f
4 touches
1 conflict
0x132b9de1…183b
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0x45b68232…9971
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 0xb465613784…635858
Audit this contract →
← previous block·next block →recent activity