← previous blocknext block →recent activity
Analyzing
Block #84,364,301
21 transactions · 17 stateful · 2026-06-29 01:21:00 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,364,301 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w010w113w015w116w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7468e81…86e5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xedf819c9…0520
0x34b655…2a6f
4 touches
1 conflict
0xf4a1cccf…0960
0x34b655…2a6f
4 touches
1 conflict
0xfd4e2262…cd8c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0c119c6d…a42e
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 0xf7468e81f0…5b86e5
Audit this contract →
← previous block·next block →recent activity