← previous blocknext block →recent activity
Analyzing
Block #102,138,360
15 transactions · 13 stateful · 2026-09-05 08:33:14 UTC
Parallelism
47/100
Blocked
69%
Avg conflicts / tx
2.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,138,360 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w39w410w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xbd590df7…9891
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
14 touches
21 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe937b6bc…8a59
0x1b6862…e19c
6 touches
3 conflicts
0x1d1eb3d2…d573
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
28 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity