← previous blocknext block →recent activity
Analyzing
Block #101,019,978
28 transactions · 24 stateful · 2026-09-01 10:36:47 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,019,978 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w28w09w110w214w116w220w322w523w624w725w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x40f0cbff…df7c
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
6 touches
3 conflicts
0x303f4ecc…ab9b
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity