← previous blocknext block →recent activity
Analyzing
Block #84,698,724
30 transactions · 17 stateful · 2026-06-30 14:30:44 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,698,724 · 30 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
11w013w016w017w118w020w226w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0x875955b6…7653
0x34b655…2a6f
6 touches
3 conflicts
0x4384dd01…4f99
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0xbebecbb6…a5fb
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity