← previous blocknext block →recent activity
Analyzing
Block #84,065,725
13 transactions · 11 stateful · 2026-06-27 16:11:57 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,065,725 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
6 touches
3 conflicts
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xe2c66a2e…150f
0x34b655…2a6f
4 touches
1 conflict
0x63f848df…7824
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x15ecb9f5…7ac2
0x40c49f…2af0
2 touches
0 conflicts
0x16a4787e…deb2
0x40c49f…2af0
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity