← previous blocknext block →recent activity
Analyzing
Block #84,355,228
13 transactions · 10 stateful · 2026-06-29 00:20:28 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,355,228 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c5c9ed…69bb
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x0a82ef74…6501
0x34b655…2a6f
2 touches
0 conflicts
0x320d2846…b3ca
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x454d8940…cfe7
0x34b655…2a6f
2 touches
0 conflicts
0x75194ada…a1c5
0x34b655…2a6f
2 touches
0 conflicts
0x75291f8b…3ac0
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 0x23c5c9ed94…3969bb
Audit this contract →
← previous block·next block →recent activity