← previous blocknext block →recent activity
Analyzing
Block #84,311,681
27 transactions · 19 stateful · 2026-06-28 19:30:15 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,311,681 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w011w012w113w014w116w117w218w319w220w423w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x5953b9da…cbb3
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x3b668f49…7dcb
0x34b655…2a6f
6 touches
3 conflicts
0x9e282197…0a1f
0x065c9d…c394
4 touches
1 conflict
0xa0cba198…ea49
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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity