← previous blocknext block →recent activity
Analyzing
Block #110,156,412
22 transactions · 20 stateful · 2026-10-03 10:28:27 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,156,412 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w010w011w112w213w315w016w119w020w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
10 touches
10 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
10 touches
10 conflicts
0x12df0148…6873
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x30690cf5…1a1f
0x34b655…2a6f
6 touches
3 conflicts
0x3b38ded9…9943
0x34b655…2a6f
6 touches
3 conflicts
0xf86cb4ee…729f
0x34b655…2a6f
5 touches
3 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
10 conflicts on slot 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity