← previous blocknext block →recent activity
Analyzing
Block #84,033,169
28 transactions · 22 stateful · 2026-06-27 12:35:03 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,033,169 · 28 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
1w02w03w14w28w19w010w111w212w313w014w115w226w127w2
- 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
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x6ac6d1bf…8b19
0x34b655…2a6f
4 touches
1 conflict
0x705f195d…cc32
0x34b655…2a6f
4 touches
1 conflict
0x8f2f9e67…3be0
0x34b655…2a6f
4 touches
1 conflict
0xac61d3a4…7da8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity