← previous blocknext block →recent activity
Analyzing
Block #84,362,261
15 transactions · 12 stateful · 2026-06-29 01:07:25 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,362,261 · 15 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
6w08w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdb71160…cb4c
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0x1b8b89d6…e2f6
0x34b655…2a6f
2 touches
0 conflicts
0x2531931d…8bd1
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x2666137c…e4ea
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 0xfdb7116008…9ccb4c
Audit this contract →
← previous block·next block →recent activity