← previous blocknext block →recent activity
Analyzing
Block #105,643,349
47 transactions · 43 stateful · 2026-09-17 15:39:34 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.81
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,643,349 · 47 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w38w49w518w631w736w1037w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
10 touches
10 conflicts
0x455da05e…510b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 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 0xb5f5f77567…50010b
Audit this contract →
← previous block·next block →recent activity