← previous blocknext block →recent activity
Analyzing
Block #84,576,753
18 transactions · 16 stateful · 2026-06-30 00:58:01 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,576,753 · 18 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
3w09w110w211w212w013w315w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9d2a96b…9b8b
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x03d57e6c…22f5
0x34b655…2a6f
4 touches
1 conflict
0x12dd43c9…22d9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x742072b0…1af8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
1 conflict on slot 0xe9d2a96be8…829b8b
Audit this contract →
← previous block·next block →recent activity