← previous blocknext block →recent activity
Analyzing
Block #105,575,074
18 transactions · 18 stateful · 2026-09-17 09:55:51 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,575,074 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w110w214w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dbacbb4…9957
0x34b655…2a6f
4 touches
1 conflict
0xa920abe6…6f3e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe97d54c5…ef6f
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x09f7f7e4…975b
0x34b655…2a6f
2 touches
0 conflicts
0x24d6bacf…5316
0x34b655…2a6f
2 touches
0 conflicts
0x28673658…a4ca
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7dbacbb47f…019957
Audit this contract →
← previous block·next block →recent activity