← previous blocknext block →recent activity
Analyzing
Block #84,354,357
14 transactions · 12 stateful · 2026-06-29 00:14:40 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,354,357 · 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
2w03w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6984da…21e5
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x56221afa…9e10
0x34b655…2a6f
2 touches
0 conflicts
0x6260a310…fd5d
0x34b655…2a6f
2 touches
0 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
2 touches
0 conflicts
0x8fcf2308…746e
0x34b655…2a6f
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 0x7c6984da0c…7821e5
Audit this contract →
← previous block·next block →recent activity