← previous blocknext block →recent activity
Analyzing
Block #84,497,677
11 transactions · 10 stateful · 2026-06-29 16:10:10 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,497,677 · 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
1w04w05w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x58f2fdac…ae86
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb2fdaf50…f34e
0x065c9d…c394
2 touches
0 conflicts
0xe421bd48…96ed
0x065c9d…c394
2 touches
0 conflicts
0xf103a7d8…badb
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity