← previous blocknext block →recent activity
Analyzing
Block #84,572,820
20 transactions · 19 stateful · 2026-06-30 00:31:47 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,572,820 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w010w312w013w115w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x6637e421…af93
0x34b655…2a6f
6 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x39619209…42e2
0x34b655…2a6f
4 touches
1 conflict
0x45b932eb…1517
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity