← previous blocknext block →recent activity
Analyzing
Block #84,698,643
25 transactions · 18 stateful · 2026-06-30 14:30:11 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,698,643 · 25 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
1w02w14w05w112w013w116w217w318w323w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0x63da0619…7a55
0x34b655…2a6f
6 touches
3 conflicts
0xea2644f5…8c97
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0x2b216760…9815
0x40c49f…2af0
4 touches
1 conflict
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity