← previous blocknext block →recent activity
Analyzing
Block #84,281,382
16 transactions · 13 stateful · 2026-06-28 16:08:21 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,281,382 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w113w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0xab86573c…682e
0x34b655…2a6f
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 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: 0x681e908b…e1ae09
1 conflict on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity