← previous blocknext block →recent activity
Analyzing
Block #84,454,550
10 transactions · 7 stateful · 2026-06-29 11:22:25 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,454,550 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x04b46154…cac9
0x065c9d…c394
2 touches
0 conflicts
0x5234b8ba…3bd2
0x065c9d…c394
2 touches
0 conflicts
0xb3098855…3539
0x065c9d…c394
2 touches
0 conflicts
0xdb07812a…e620
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity