← previous blocknext block →recent activity
Analyzing
Block #84,114,531
21 transactions · 18 stateful · 2026-06-27 21:37:09 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,114,531 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w110w011w112w213w314w417w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe1e58d05…117f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x99246de6…5bd5
0x34b655…2a6f
5 touches
3 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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity