← previous blocknext block →recent activity
Analyzing
Block #84,543,614
8 transactions · 7 stateful · 2026-06-29 21:16:45 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,543,614 · 8 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
1w02w03w14w25w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41459352…4149
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x78c30df4…c54d
0xa6afd3…d132
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x9ff2b017…3fa2
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x393dfd73…ff57
0x34b655…2a6f
2 touches
0 conflicts
0xc0be9369…d103
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 0x4145935245…f14149
Audit this contract →
← previous block·next block →recent activity