← previous blocknext block →recent activity
Analyzing
Block #84,528,402
14 transactions · 12 stateful · 2026-06-29 19:35:05 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,528,402 · 14 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
5w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0x909c2852…f823
0x34b655…2a6f
4 touches
1 conflict
0x0d966d04…db69
0x34b655…2a6f
2 touches
0 conflicts
0x0f44b5ba…e7bf
0x34b655…2a6f
2 touches
0 conflicts
0x14157f8f…a72c
0x34b655…2a6f
2 touches
0 conflicts
0x2a9c0c09…ce85
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
1 conflict on slot 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity