← previous blocknext block →recent activity
Analyzing
Block #102,231,740
18 transactions · 17 stateful · 2026-09-05 16:26:25 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,231,740 · 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
1w02w13w04w15w28w09w111w213w014w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0xc52785b9…08f8
0x34b655…2a6f
6 touches
3 conflicts
0xddf10453…d774
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
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
3 conflicts on slot 0xfd713bab1a…98a651
Audit this contract →
← previous block·next block →recent activity