← previous blocknext block →recent activity
Analyzing
Block #105,760,260
12 transactions · 12 stateful · 2026-09-18 01:27:58 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,760,260 · 12 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
1w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06fce24…887d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x4847c505…b303
0x34b655…2a6f
4 touches
1 conflict
0x2a0eb1f4…5986
0x34b655…2a6f
2 touches
0 conflicts
0x4d971bc9…fadc
0x34b655…2a6f
2 touches
0 conflicts
0x4d971bc9…fadd
0x34b655…2a6f
2 touches
0 conflicts
0x6b1af8f1…22f1
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 0xf06fce24b3…55887d
Audit this contract →
← previous block·next block →recent activity