← previous blocknext block →recent activity
Analyzing
Block #84,060,841
19 transactions · 17 stateful · 2026-06-27 15:39:31 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,060,841 · 19 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
1w02w13w24w35w16w08w19w210w311w012w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31658946…5d47
0x34b655…2a6f
8 touches
6 conflicts
0x8b1d9d2d…0fe3
0xd32edf…ff58
7 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x785889c9…0603
0x34b655…2a6f
6 touches
3 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
6 touches
3 conflicts
0x93afca4c…b47c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x3165894656…cc5d47
Audit this contract →
← previous block·next block →recent activity