← previous blocknext block →recent activity
Analyzing
Block #84,332,445
30 transactions · 25 stateful · 2026-06-28 21:48:36 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,332,445 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w18w110w011w112w213w314w415w117w018w119w321w226w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xcfe15fba…4f97
0x34b655…2a6f
10 touches
10 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x8fcf2308…746e
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity