← previous blocknext block →recent activity
Analyzing
Block #84,698,861
20 transactions · 17 stateful · 2026-06-30 14:31:38 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,698,861 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w111w013w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x587911c7…9e01
0x34b655…2a6f
5 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x0ccb39ed…3680
0x34b655…2a6f
4 touches
1 conflict
0x19e6b3a8…ba29
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
6 conflicts on slot 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity