← previous blocknext block →recent activity
Analyzing
Block #102,016,873
22 transactions · 21 stateful · 2026-09-04 22:17:27 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,016,873 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w27w38w49w514w015w017w118w219w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4f6a526…ad10
0x34b655…2a6f
10 touches
10 conflicts
0x02372d42…1871
0x34b655…2a6f
10 touches
10 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
10 touches
10 conflicts
0x53e08444…d671
0x34b655…2a6f
10 touches
10 conflicts
0x7c216fca…20cb
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0x999c658d…b185
0x34b655…2a6f
10 touches
10 conflicts
0x9c088939…ddd7
0x34b655…2a6f
10 touches
10 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 0xd4f6a52629…b0ad10
Audit this contract →
← previous block·next block →recent activity