← previous blocknext block →recent activity
Analyzing
Block #102,476,112
28 transactions · 26 stateful · 2026-09-06 13:04:32 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,476,112 · 28 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
1w02w19w011w012w116w217w322w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
6 touches
3 conflicts
0x827d4095…2169
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x41aa4da3…3a1a
0x34b655…2a6f
5 touches
3 conflicts
0x4cd5b8da…066b
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity