← previous blocknext block →recent activity
Analyzing
Block #84,351,472
16 transactions · 11 stateful · 2026-06-28 23:55:24 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,351,472 · 16 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
6w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xcde75077…ccee
0x34b655…2a6f
4 touches
1 conflict
0x314f7c9c…eb08
0x34b655…2a6f
3 touches
1 conflict
0x38523b4b…90ab
0x065c9d…c394
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
2 touches
0 conflicts
0xf1ed77a2…1e3d
0x065c9d…c394
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity