← previous blocknext block →recent activity
Analyzing
Block #84,358,658
29 transactions · 18 stateful · 2026-06-29 00:43:22 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,358,658 · 29 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
1w06w07w19w213w014w115w216w317w420w021w222w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xb7a3240c…dd63
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
6 touches
3 conflicts
0xcffc17bc…3544
0x34b655…2a6f
6 touches
3 conflicts
0x8d8c3670…c0ce
0xd32edf…ff58
5 touches
3 conflicts
0x830bee06…a264
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity