← previous blocknext block →recent activity
Analyzing
Block #84,545,103
20 transactions · 17 stateful · 2026-06-29 21:26:46 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,545,103 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x58c659ec…3c6c
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x69ed69b2…dfff
0x065c9d…c394
2 touches
0 conflicts
0x7dd19a8f…69e3
0x065c9d…c394
2 touches
0 conflicts
0xaeed7905…ba5d
0x065c9d…c394
2 touches
0 conflicts
0xdb1ee6a3…627b
0x065c9d…c394
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity