← previous blocknext block →recent activity
Analyzing
Block #84,351,668
18 transactions · 18 stateful · 2026-06-28 23:56:43 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,351,668 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w013w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcde75077…ccee
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa6fd7409…16b7
0x8fbe07…71b6
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x82d83939…0e52
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c0
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0xcde75077a7…6dccee
Audit this contract →
← previous block·next block →recent activity