← previous blocknext block →recent activity
Analyzing
Block #84,024,283
28 transactions · 22 stateful · 2026-06-27 11:35:56 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,024,283 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w18w29w311w412w514w015w616w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xe8370d49…b810
0x34b655…2a6f
6 touches
3 conflicts
0xe27b0bdf…b21a
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0x5df6102c…6494
0xa6afd3…d132
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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