← previous blocknext block →recent activity
Analyzing
Block #101,025,987
29 transactions · 20 stateful · 2026-09-01 11:07:02 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,025,987 · 29 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
1w04w15w06w18w09w110w220w221w325w026w127w028w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4405999c…165e
0x34b655…2a6f
8 touches
6 conflicts
0x24b08f9c…e594
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
6 touches
3 conflicts
0x72b31f58…619a
0x34b655…2a6f
6 touches
3 conflicts
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
6 conflicts on slot 0x4405999c9b…f1165e
Audit this contract →
← previous block·next block →recent activity