← previous blocknext block →recent activity
Analyzing
Block #84,493,741
23 transactions · 15 stateful · 2026-06-29 15:43:56 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,493,741 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w211w012w113w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x3dec32b2…b3ad
0x34b655…2a6f
4 touches
1 conflict
0x44966858…1d1a
0x34b655…2a6f
4 touches
1 conflict
0x5fb0ac58…9498
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x8f4c5cb2…cbee
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity