← previous blocknext block →recent activity
Analyzing
Block #84,331,685
14 transactions · 12 stateful · 2026-06-28 21:43:33 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,331,685 · 14 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
5w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0xb577a4a7…a670
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
3 conflicts on slot 0x5d7f309de2…775145
Audit this contract →
← previous block·next block →recent activity