← previous blocknext block →recent activity
Analyzing
Block #105,627,315
22 transactions · 21 stateful · 2026-09-17 14:18:51 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,627,315 · 22 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
1w02w03w14w25w37w08w19w213w014w115w016w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0d2c160…e188
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x427aa12f…e796
0x34b655…2a6f
4 touches
1 conflict
0x4ab195e7…0967
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 0xb0d2c160ab…d1e188
Audit this contract →
← previous block·next block →recent activity