← previous blocknext block →recent activity
Analyzing
Block #84,335,205
22 transactions · 18 stateful · 2026-06-28 22:06:58 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,335,205 · 22 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
3w04w05w17w28w311w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bdcc5ee…7e90
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf1ee12f4…867f
0x34b655…2a6f
4 touches
1 conflict
0xf3db4154…57f1
0x40c49f…2af0
4 touches
1 conflict
0x03e24ec6…4a23
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 0x4bdcc5eebf…627e90
Audit this contract →
← previous block·next block →recent activity