← previous blocknext block →recent activity
Analyzing
Block #102,570,994
16 transactions · 13 stateful · 2026-09-06 21:05:49 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,570,994 · 16 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
1w02w18w212w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2be8f87c…30ab
0x34b655…2a6f
2 touches
0 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
2 touches
0 conflicts
0x53c41998…7d52
0x34b655…2a6f
2 touches
0 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
2 touches
0 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity