← previous blocknext block →recent activity
Analyzing
Block #105,627,396
17 transactions · 16 stateful · 2026-09-17 14:19:15 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,627,396 · 17 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
2w03w14w25w36w07w08w49w511w112w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf10298ad…32a7
0x34b655…2a6f
10 touches
10 conflicts
0x7151b1ad…4520
0x34b655…2a6f
8 touches
6 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x61517790…ce3f
0x34b655…2a6f
4 touches
1 conflict
0x678143da…dc6b
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
10 conflicts on slot 0xf10298ad02…bd32a7
Audit this contract →
← previous block·next block →recent activity