← previous blocknext block →recent activity
Analyzing
Block #101,673,297
13 transactions · 13 stateful · 2026-09-03 17:24:03 UTC
Parallelism
39/100
Blocked
54%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,673,297 · 13 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
1w02w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28eed2ad…c4b2
0x34b655…2a6f
10 touches
10 conflicts
0x28eed2ad…c4b3
0x34b655…2a6f
10 touches
10 conflicts
0xee8237bd…46ad
0x34b655…2a6f
10 touches
10 conflicts
0xcff5eb3b…44b1
0x34b655…2a6f
10 touches
10 conflicts
0x95b74d82…e4e0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x110a3804…f842
0x34b655…2a6f
6 touches
3 conflicts
0xa4dfe994…e3d0
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
10 conflicts on slot 0x28eed2ad33…59c4b2
Audit this contract →
← previous block·next block →recent activity