← previous blocknext block →recent activity
Analyzing
Block #102,188,495
20 transactions · 19 stateful · 2026-09-05 12:47:24 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,188,495 · 20 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
1w02w13w24w05w16w27w39w213w217w018w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f749304…d1c1
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x8feb2121…031a
0x34b655…2a6f
8 touches
6 conflicts
0x9d7ac3b9…22f8
0x34b655…2a6f
8 touches
6 conflicts
0xc9ca92b3…ac3f
0x34b655…2a6f
8 touches
6 conflicts
0x3a3097d7…2ab8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1c1d227d…4ff1
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
6 conflicts on slot 0x5f7493049f…edd1c1
Audit this contract →
← previous block·next block →recent activity