← previous blocknext block →recent activity
Analyzing
Block #102,066,743
30 transactions · 20 stateful · 2026-09-05 02:30:01 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,066,743 · 30 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
1w02w05w17w28w110w212w013w115w016w117w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71b395d9…1697
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1c345590…14e7
0x34b655…2a6f
6 touches
3 conflicts
0x26fa2369…f4a1
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0x71b395d942…4d1697
Audit this contract →
← previous block·next block →recent activity