← previous blocknext block →recent activity
Analyzing
Block #84,040,868
11 transactions · 9 stateful · 2026-06-27 13:26:26 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,040,868 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd77e6c1…264b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x24e133eb…b3c5
0x34b655…2a6f
2 touches
0 conflicts
0x28e30e37…e4f6
0x34b655…2a6f
2 touches
0 conflicts
0x3b428d1b…103b
0x34b655…2a6f
2 touches
0 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
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 0xfd77e6c174…b2264b
Audit this contract →
← previous block·next block →recent activity