← previous blocknext block →recent activity
Analyzing
Block #84,319,150
23 transactions · 18 stateful · 2026-06-28 20:20:00 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,319,150 · 23 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
1w04w07w08w19w210w311w415w116w217w018w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x75194ada…a1c5
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x1bfa36e2…5ec9
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