← previous blocknext block →recent activity
Analyzing
Block #110,393,264
14 transactions · 13 stateful · 2026-10-04 06:20:12 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,393,264 · 14 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
6w07w110w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdf23360e…3531
0x34b655…2a6f
6 touches
3 conflicts
0xf7b1dfd2…9c5e
0x34b655…2a6f
4 touches
1 conflict
0xacfe9a3d…4bdc
0x34b655…2a6f
4 touches
1 conflict
0x0fcb5a25…9f42
0x34b655…2a6f
4 touches
1 conflict
0x491eabf8…9dc2
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x87d55966…bd15
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity