← previous blocknext block →recent activity
Analyzing
Block #84,564,055
12 transactions · 12 stateful · 2026-06-29 23:33:20 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,564,055 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f636f7a…af74
0x34b655…2a6f
6 touches
3 conflicts
0x6e942750…9953
0x34b655…2a6f
6 touches
3 conflicts
0xa7e45018…b59c
0x34b655…2a6f
6 touches
3 conflicts
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3891cd1c…e740
0x34b655…2a6f
4 touches
1 conflict
0x4da87506…fdf1
0x34b655…2a6f
4 touches
1 conflict
0x549f612f…0565
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
3 conflicts on slot 0x0f636f7a91…03af74
Audit this contract →
← previous block·next block →recent activity