← previous blocknext block →recent activity
Analyzing
Block #102,104,359
28 transactions · 25 stateful · 2026-09-05 05:40:56 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,104,359 · 28 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
1w03w04w15w213w018w120w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x5dd033b6…34b5
0x34b655…2a6f
8 touches
6 conflicts
0x515ea6bd…08ea
0x34b655…2a6f
6 touches
3 conflicts
0xf6c51b4c…6278
0x34b655…2a6f
6 touches
3 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0xf5d28bce…c32c
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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity