← previous blocknext block →recent activity
Analyzing
Block #102,055,928
25 transactions · 21 stateful · 2026-09-05 01:35:13 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,055,928 · 25 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
1w04w05w16w27w38w410w115w218w320w123w224w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dffc33e…068d
0x34b655…2a6f
8 touches
6 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
8 touches
6 conflicts
0x3d13406e…eff1
0x34b655…2a6f
8 touches
6 conflicts
0x898a08aa…c855
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x4dffc33e8c…39068d
Audit this contract →
← previous block·next block →recent activity