← previous blocknext block →recent activity
Analyzing
Block #84,494,242
21 transactions · 17 stateful · 2026-06-29 15:47:16 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,494,242 · 21 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
1w02w15w06w17w28w311w012w113w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x44966858…1d1a
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
6 touches
3 conflicts
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0xbf0e051a…10a0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity