← previous blocknext block →recent activity
Analyzing
Block #105,921,442
28 transactions · 21 stateful · 2026-09-18 15:01:30 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,921,442 · 28 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
8w09w117w019w221w125w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xeec0853a…da8e
0xa6afd3…d132
4 touches
1 conflict
0x3e4486b9…fa99
0x34b655…2a6f
4 touches
1 conflict
0x4d63bc0a…65d8
0x34b655…2a6f
4 touches
1 conflict
0x885efce3…7496
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity