← previous blocknext block →recent activity
Analyzing
Block #84,102,574
10 transactions · 9 stateful · 2026-06-27 20:17:34 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,102,574 · 10 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
1w02w13w04w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98e95e72…24dd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x4fa4d904…44a1
0x34b655…2a6f
2 touches
0 conflicts
0x075f3c76…6b85
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0b60b7cf…a282
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 0x98e95e72e9…0324dd
Audit this contract →
← previous block·next block →recent activity