← previous blocknext block →recent activity
Analyzing
Block #102,137,381
20 transactions · 20 stateful · 2026-09-05 08:28:17 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,137,381 · 20 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
1w02w16w19w110w212w313w414w516w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbceecf11…0120
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8e03e4de…4bf8
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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 0xbceecf11eb…fc0120
Audit this contract →
← previous block·next block →recent activity