← previous blocknext block →recent activity
Analyzing
Block #84,352,183
23 transactions · 18 stateful · 2026-06-29 00:00:09 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,352,183 · 23 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
1w02w13w24w39w010w111w213w016w118w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8f0e8a2f…a850
0x34b655…2a6f
6 touches
3 conflicts
0xd8a49b87…5d96
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x403d1735…de44
0x34b655…2a6f
4 touches
1 conflict
0x4979bbd7…6d40
0x34b655…2a6f
4 touches
1 conflict
0x5bfcd22f…9103
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity