← previous blocknext block →recent activity
Analyzing
Block #84,106,909
15 transactions · 13 stateful · 2026-06-27 20:46:25 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,106,909 · 15 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
5w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x672fd8ba…9e9e
0x34b655…2a6f
8 touches
6 conflicts
0xe99ebc4d…22f9
0x34b655…2a6f
6 touches
3 conflicts
0x02c96442…1404
0x34b655…2a6f
6 touches
3 conflicts
0x8a765297…36fb
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x672fd8ba57…cf9e9e
Audit this contract →
← previous block·next block →recent activity