← previous blocknext block →recent activity
Analyzing
Block #84,570,896
12 transactions · 12 stateful · 2026-06-30 00:18:59 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,570,896 · 12 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
4w05w16w28w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4702f73…926c
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7bc74ef3…0fee
0x34b655…2a6f
6 touches
3 conflicts
0x3a395c73…35de
0x34b655…2a6f
4 touches
1 conflict
0x4559eca9…7148
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x8a55cfe8…8ce3
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 0xd4702f73d1…46926c
Audit this contract →
← previous block·next block →recent activity