← previous blocknext block →recent activity
Analyzing
Block #84,498,963
13 transactions · 11 stateful · 2026-06-29 16:18:46 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,498,963 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc8536f01…eb88
0x34b655…2a6f
4 touches
1 conflict
0x71eb60eb…cf8a
0x34b655…2a6f
4 touches
1 conflict
0x2e37b5c0…d6a1
0x34b655…2a6f
2 touches
0 conflicts
0x5a27ab8f…74ca
0x34b655…2a6f
2 touches
0 conflicts
0x5e87912c…7836
0x34b655…2a6f
2 touches
0 conflicts
0x67fc285e…2584
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity