← previous blocknext block →recent activity
Analyzing
Block #105,539,164
37 transactions · 28 stateful · 2026-09-17 06:55:07 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,539,164 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w411w012w513w615w116w217w325w426w527w628w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x0b234df0…aee3
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0xb4b50f93…93e2
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xc948dbdcb8…f4199a
Audit this contract →
← previous block·next block →recent activity