← previous blocknext block →recent activity
Analyzing
Block #84,004,185
28 transactions · 25 stateful · 2026-06-27 09:22:02 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,004,185 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w213w315w018w119w120w221w022w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0x8f2f9e67…3be0
0x34b655…2a6f
6 touches
3 conflicts
0xe8370d49…b810
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3be12d17…236e
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity