← previous blocknext block →recent activity
Analyzing
Block #84,136,503
14 transactions · 12 stateful · 2026-06-28 00:03:28 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,136,503 · 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
5w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0592331…1e7f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0xf1ec84ef…466b
0x34b655…2a6f
4 touches
1 conflict
0x130b8bf2…8fd7
0x34b655…2a6f
4 touches
1 conflict
0x19bfb0e5…73b4
0x34b655…2a6f
4 touches
1 conflict
0x20f21193…f30d
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
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 0xa059233109…d51e7f
Audit this contract →
← previous block·next block →recent activity