← previous blocknext block →recent activity
Analyzing
Block #84,495,872
22 transactions · 19 stateful · 2026-06-29 15:58:09 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,495,872 · 22 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
1w02w13w010w011w112w213w315w116w217w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742436a7…c4d4
0x34b655…2a6f
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x9ad4d28a…c788
0x34b655…2a6f
6 touches
3 conflicts
0xb6836671…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
6 touches
3 conflicts
0xd3666b7d…0a5f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x742436a7e5…69c4d4
Audit this contract →
← previous block·next block →recent activity