← previous blocknext block →recent activity
Analyzing
Block #102,063,826
21 transactions · 21 stateful · 2026-09-05 02:15:15 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,063,826 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0x999c658d…b185
0x34b655…2a6f
6 touches
3 conflicts
0x79ec4509…1f61
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
0x34b655…2a6f
6 touches
3 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
6 touches
3 conflicts
0xf5d28bce…c32c
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 0x987859bea4…3e2686
Audit this contract →
← previous block·next block →recent activity