← previous blocknext block →recent activity
Analyzing
Block #100,124,262
14 transactions · 14 stateful · 2026-08-29 07:25:58 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,124,262 · 14 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
1w02w14w05w16w07w28w19w311w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc20bb30f…7331
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
6 touches
3 conflicts
0xb9286307…9908
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xc20bb30fb9…f17331
Audit this contract →
← previous block·next block →recent activity