← previous blocknext block →recent activity
Analyzing
Block #84,307,137
18 transactions · 18 stateful · 2026-06-28 19:00:04 UTC
Parallelism
78/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,307,137 · 18 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
4w05w16w07w29w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x1e346a85…e9c5
0x34b655…2a6f
4 touches
1 conflict
0x0833f1ab…71e7
0x34b655…2a6f
2 touches
0 conflicts
0x25a70b16…e1df
0x34b655…2a6f
2 touches
0 conflicts
0x7c6984da…21e5
0x34b655…2a6f
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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity