← previous blocknext block →recent activity
Analyzing
Block #102,191,640
20 transactions · 18 stateful · 2026-09-05 13:03:19 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,191,640 · 20 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
1w02w13w04w15w26w37w48w510w014w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xfa805f95…72a4
0x34b655…2a6f
10 touches
10 conflicts
0xc9ca92b3…ac3f
0x34b655…2a6f
10 touches
10 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
10 touches
10 conflicts
0x56e0d685…c960
0x34b655…2a6f
10 touches
10 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
10 touches
10 conflicts
0x5f749304…d1c1
0x34b655…2a6f
10 touches
10 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
10 touches
10 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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity