← previous blocknext block →recent activity
Analyzing
Block #84,575,118
14 transactions · 13 stateful · 2026-06-30 00:47:07 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,575,118 · 14 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
4w05w111w212w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97fe3267…5e87
0x34b655…2a6f
8 touches
6 conflicts
0xdcf90674…5bf6
0x34b655…2a6f
8 touches
6 conflicts
0xa9ad4c70…1120
0x34b655…2a6f
6 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x5337754c…a27f
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x6f416797…c8de
0x34b655…2a6f
4 touches
1 conflict
0x712f13a9…bee0
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
6 conflicts on slot 0x97fe32673b…cb5e87
Audit this contract →
← previous block·next block →recent activity