← previous blocknext block →recent activity
Analyzing
Block #84,594,861
21 transactions · 21 stateful · 2026-06-30 02:58:38 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,594,861 · 21 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
1w02w18w09w110w011w114w016w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7585925a…3f45
0x34b655…2a6f
10 touches
10 conflicts
0x7f93f2f0…6666
0x34b655…2a6f
8 touches
6 conflicts
0xd7e72076…294a
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0x32329fca…2d8c
0x34b655…2a6f
6 touches
3 conflicts
0xe99ebc4d…22f9
0x34b655…2a6f
6 touches
3 conflicts
0xdde8af9d…1bef
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity