← previous blocknext block →recent activity
Analyzing
Block #84,492,627
23 transactions · 19 stateful · 2026-06-29 15:36:29 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,492,627 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w210w311w412w314w516w118w221w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
8 touches
6 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0x44966858…1d1a
0x34b655…2a6f
4 touches
1 conflict
0x62554ce4…109e
0x34b655…2a6f
4 touches
1 conflict
0x84ecc4df…a944
0x34b655…2a6f
4 touches
1 conflict
0xbb96f8af…205f
0x34b655…2a6f
4 touches
1 conflict
0xf95f86cd…e927
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity