← previous blocknext block →recent activity
Analyzing
Block #84,290,209
16 transactions · 16 stateful · 2026-06-28 17:07:12 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,290,209 · 16 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
1w02w15w08w29w210w312w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x6a712218…4c32
0x065c9d…c394
4 touches
1 conflict
0xea1b6f06…49e8
0x065c9d…c394
4 touches
1 conflict
0xa98e23f1…2e75
0x34b655…2a6f
4 touches
1 conflict
0xab621973…cc16
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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity