← previous blocknext block →recent activity
Analyzing
Block #84,357,944
14 transactions · 13 stateful · 2026-06-29 00:38:36 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,357,944 · 14 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
4w06w07w08w19w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b8acfe4…a3d9
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7263b4fb…09dc
0xa6afd3…d132
4 touches
1 conflict
0xda47a23d…57e3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
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 0x3b8acfe4d6…e0a3d9
Audit this contract →
← previous block·next block →recent activity