← previous blocknext block →recent activity
Analyzing
Block #84,621,504
11 transactions · 6 stateful · 2026-06-30 05:56:06 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,621,504 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
4 touches
1 conflict
0x4384dd01…4f99
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x125f8322…94f1
0x34b655…2a6f
2 touches
0 conflicts
0x159b8597…48a4
0x34b655…2a6f
2 touches
0 conflicts
0x2077ae32…f620
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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
1 conflict on slot 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity