← previous blocknext block →recent activity
Analyzing
Block #84,457,504
37 transactions · 24 stateful · 2026-06-29 11:42:07 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,457,504 · 37 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w221w022w123w224w325w432w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x9ad4d28a…c788
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x53e50026…6d8c
0x69df8a…6292
4 touches
1 conflict
0x7f4a8466…f2cc
0x69df8a…6292
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