← previous blocknext block →recent activity
Analyzing
Block #106,810,189
18 transactions · 18 stateful · 2026-09-21 17:35:40 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,810,189 · 18 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
1w02w03w15w06w18w09w111w112w213w314w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9c1bb1a…45de
0x34b655…2a6f
8 touches
6 conflicts
0x7d7bbecf…635a
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x8f0f4fae…16dc
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x3e4486b9…fa99
0x34b655…2a6f
4 touches
1 conflict
0x4856b443…1824
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xd9c1bb1aeb…e145de
Audit this contract →
← previous block·next block →recent activity