← previous blocknext block →recent activity
Analyzing
Block #84,571,010
13 transactions · 12 stateful · 2026-06-30 00:19:44 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,571,010 · 13 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
5w06w17w28w09w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0xb9bc1dfc…6bfb
0x34b655…2a6f
6 touches
3 conflicts
0x26918bca…6c75
0x34b655…2a6f
6 touches
3 conflicts
0xc1aad6e5…9135
0x34b655…2a6f
4 touches
2 conflicts
0x3ed01bdd…b317
0x34b655…2a6f
4 touches
1 conflict
0x4da995bd…d5ef
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
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
3 conflicts on slot 0x70638c2476…811553
Audit this contract →
← previous block·next block →recent activity