← previous blocknext block →recent activity
Analyzing
Block #106,053,924
22 transactions · 18 stateful · 2026-09-19 02:08:26 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,053,924 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w115w116w217w219w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x46a5d79e…3d63
0x34b655…2a6f
6 touches
3 conflicts
0xddd20e39…d524
0x34b655…2a6f
6 touches
3 conflicts
0x7c30bd77…61ae
0x34b655…2a6f
4 touches
1 conflict
0x888288e6…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
3 conflicts on slot 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity