← previous blocknext block →recent activity
Analyzing
Block #105,600,560
24 transactions · 24 stateful · 2026-09-17 12:04:08 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,600,560 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w27w08w09w115w317w118w119w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xf0a8a215…8f23
0x851145…3f07
6 touches
3 conflicts
0x35c68080…aace
0x851145…3f07
6 touches
3 conflicts
0xd6265424…0d3a
0x851145…3f07
6 touches
3 conflicts
0x209fe554…d2d3
0x851145…3f07
5 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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity