← previous blocknext block →recent activity
Analyzing
Block #102,061,641
15 transactions · 15 stateful · 2026-09-05 02:04:10 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,061,641 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w010w111w212w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac27d4e9…fffc
0x34b655…2a6f
6 touches
3 conflicts
0x3167d7d8…a06b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x762c1397…c4dd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x394c3833…b4ab
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0ec07cf7…c0c9
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 0xac27d4e99a…c3fffc
Audit this contract →
← previous block·next block →recent activity