← previous blocknext block →recent activity
Analyzing
Block #102,468,164
29 transactions · 25 stateful · 2026-09-06 12:24:19 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,468,164 · 29 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
2w04w05w16w27w09w112w213w315w321w422w423w524w325w426w427w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0xc5dfe7d0…a62e
0x34b655…2a6f
8 touches
6 conflicts
0x83e86297…825e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x0747620e…9782
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity