← previous blocknext block →recent activity
Analyzing
Block #106,036,042
13 transactions · 12 stateful · 2026-09-19 00:38:27 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,036,042 · 13 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
1w06w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0xc3771f33…3f33
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0xb935707a…140f
0x34b655…2a6f
4 touches
1 conflict
0x662e354e…e306
0x34b655…2a6f
2 touches
0 conflicts
0x6696442e…a469
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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 0xbaf6ed88a9…dec179
Audit this contract →
← previous block·next block →recent activity