← previous blocknext block →recent activity
Analyzing
Block #84,318,627
9 transactions · 9 stateful · 2026-06-28 20:16:30 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,318,627 · 9 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x6fb323ed…337d
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xa636a0d4…ec3c
0x34b655…2a6f
3 touches
1 conflict
0xaec3354f…3cd2
0x065c9d…c394
2 touches
0 conflicts
0xf5ae0320…8977
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity