← previous blocknext block →recent activity
Analyzing
Block #102,372,177
18 transactions · 18 stateful · 2026-09-06 04:18:00 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,372,177 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w212w313w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
10 touches
10 conflicts
0xf547aa3c…06e6
0x34b655…2a6f
6 touches
3 conflicts
0xa9502360…b9bd
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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
10 conflicts on slot 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity