← previous blocknext block →recent activity
Analyzing
Block #105,852,092
19 transactions · 18 stateful · 2026-09-18 09:11:35 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,852,092 · 19 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
2w04w09w110w111w212w213w314w415w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdc9915b5…542c
0x34b655…2a6f
10 touches
10 conflicts
0x3a87488e…9275
0x34b655…2a6f
10 touches
10 conflicts
0x4f1d8ea3…03ae
0x34b655…2a6f
8 touches
6 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0x3ad04ce1…1904
0xa6afd3…d132
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity