← previous blocknext block →recent activity
Analyzing
Block #105,846,224
17 transactions · 17 stateful · 2026-09-18 08:42:04 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,846,224 · 17 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
1w02w03w14w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69bf73eb…fe40
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
10 touches
10 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x6194cf1e…0c42
0x34b655…2a6f
4 touches
1 conflict
0x1470cae0…177e
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
15 conflicts on slot 0x69bf73eb51…5dfe40
Audit this contract →
← previous block·next block →recent activity