← previous blocknext block →recent activity
Analyzing
Block #102,284,251
20 transactions · 17 stateful · 2026-09-05 20:52:40 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,284,251 · 20 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
1w02w13w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0xb73a5ffd…ddee
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x179b31b3…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x3a371191…31c4
0x34b655…2a6f
4 touches
1 conflict
0x45cf6323…cc19
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x4ab70ccd…2683
0x34b655…2a6f
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
3 conflicts on slot 0x987859bea4…3e2686
Audit this contract →
← previous block·next block →recent activity