← previous blocknext block →recent activity
Analyzing
Block #105,634,040
11 transactions · 10 stateful · 2026-09-17 14:52:42 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,634,040 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3b620ed…64f4
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x941bd594…21fd
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e49c9…7833
0x34b655…2a6f
2 touches
0 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
2 touches
0 conflicts
0x7b6d2deb…dde0
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 0xb3b620ede1…4864f4
Audit this contract →
← previous block·next block →recent activity