← previous blocknext block →recent activity
Analyzing
Block #101,020,529
18 transactions · 14 stateful · 2026-09-01 10:39:33 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,020,529 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w313w414w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e135144…4167
0x34b655…2a6f
10 touches
10 conflicts
0xf13996a1…9c88
0x34b655…2a6f
10 touches
10 conflicts
0x9c83a7b1…e305
0x34b655…2a6f
10 touches
10 conflicts
0x14fdfaf5…4469
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x5434835d…650f
0x34b655…2a6f
8 touches
6 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
8 touches
6 conflicts
0x5f053696…4e0f
0x065c9d…c394
4 touches
1 conflict
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
10 conflicts on slot 0x4e135144ab…684167
Audit this contract →
← previous block·next block →recent activity