← previous blocknext block →recent activity
Analyzing
Block #102,707,094
13 transactions · 11 stateful · 2026-09-07 08:32:30 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,707,094 · 13 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
2w05w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a6bc99…a848
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x71b395d9…1697
0x34b655…2a6f
6 touches
3 conflicts
0xada087b9…4aca
0x34b655…2a6f
4 touches
1 conflict
0x06594187…490e
0x065c9d…c394
2 touches
0 conflicts
0x19980544…e962
0x065c9d…c394
2 touches
0 conflicts
0x517a3bdd…c81a
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0xb5a6bc9906…fea848
Audit this contract →
← previous block·next block →recent activity