← previous blocknext block →recent activity
Analyzing
Block #105,539,990
19 transactions · 19 stateful · 2026-09-17 06:59:16 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,539,990 · 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
1w02w14w05w16w212w213w014w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44e63285…417c
0x34b655…2a6f
12 touches
15 conflicts
0x178a61ad…4958
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x70f537e8…399b
0x34b655…2a6f
8 touches
6 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
8 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
15 conflicts on slot 0x44e632854d…d8417c
Audit this contract →
← previous block·next block →recent activity