← previous blocknext block →recent activity
Analyzing
Block #105,921,241
27 transactions · 25 stateful · 2026-09-18 15:00:30 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,921,241 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w08w211w012w113w114w015w117w319w020w121w123w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x5a34952d…7977
0x065c9d…c394
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x110a3804…f842
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x23ee9bad…c511
0x34b655…2a6f
4 touches
1 conflict
0x33303721…96ed
0x34b655…2a6f
4 touches
1 conflict
0x377ea90e…e6c2
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity