← previous blocknext block →recent activity
Analyzing
Block #84,318,339
17 transactions · 16 stateful · 2026-06-28 20:14:34 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,318,339 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w08w19w210w111w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x03b4fefa…9a00
0x34b655…2a6f
4 touches
1 conflict
0x0617a00a…537d
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x1956ef6e…81e4
0x34b655…2a6f
4 touches
1 conflict
0x2754e960…bcc1
0x34b655…2a6f
4 touches
1 conflict
0x369a11e2…566f
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
3 conflicts on slot 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity