← previous blocknext block →recent activity
Analyzing
Block #84,358,540
32 transactions · 22 stateful · 2026-06-29 00:42:35 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,358,540 · 32 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
8w09w110w011w113w014w115w016w117w221w322w124w225w129w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7534f53d…6ed4
0x34b655…2a6f
10 touches
10 conflicts
0xa0137b0d…6d34
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0x753da1ce…6bbd
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
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 0x7534f53d7a…5a6ed4
Audit this contract →
← previous block·next block →recent activity