← previous blocknext block →recent activity
Analyzing
Block #105,849,517
19 transactions · 19 stateful · 2026-09-18 08:58:38 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,849,517 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf191067f…59ce
0x34b655…2a6f
16 touches
28 conflicts
0x2827ae77…4368
0x34b655…2a6f
14 touches
21 conflicts
0xf173d295…4e87
0x34b655…2a6f
12 touches
15 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xc10b903d…2f54
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0xe135588e…812f
0x34b655…2a6f
6 touches
3 conflicts
0x0f94e353…1f32
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xf191067f69…9e59ce
Audit this contract →
← previous block·next block →recent activity