← previous blocknext block →recent activity
Analyzing
Block #84,039,927
17 transactions · 16 stateful · 2026-06-27 13:20:09 UTC
Parallelism
53/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,039,927 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w18w29w210w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
12 touches
15 conflicts
0x562b8381…cef9
0x34b655…2a6f
10 touches
10 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 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: Perpl
15 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity