← previous blocknext block →recent activity
Analyzing
Block #102,038,893
42 transactions · 42 stateful · 2026-09-05 00:08:57 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,038,893 · 42 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w125w340w441w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xfd713bab…a651
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0x67043b0b…97d7
0x34b655…2a6f
12 touches
15 conflicts
0x6823c28e…594c
0x34b655…2a6f
12 touches
15 conflicts
0x79ec4509…1f61
0x34b655…2a6f
12 touches
15 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
12 touches
15 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity