← previous blocknext block →recent activity
Analyzing
Block #105,643,539
33 transactions · 26 stateful · 2026-09-17 15:40:31 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,643,539 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w223w426w327w428w529w632w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeddebb1d…4dd4
0x34b655…2a6f
12 touches
15 conflicts
0x678143da…dc6b
0x34b655…2a6f
10 touches
10 conflicts
0x4f403872…f1e7
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc7559235…1215
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xeddebb1d0b…f54dd4
Audit this contract →
← previous block·next block →recent activity