← previous blocknext block →recent activity
Analyzing
Block #84,255,418
8 transactions · 5 stateful · 2026-06-28 13:15:23 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,255,418 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0a5d0d7d…c5f2
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
2 touches
0 conflicts
0x826cce18…251c
0x34b655…2a6f
2 touches
0 conflicts
0x860cda0b…b1b7
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity