← previous blocknext block →recent activity
Analyzing
Block #84,497,893
22 transactions · 21 stateful · 2026-06-29 16:11:37 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,497,893 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w010w011w112w113w417w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xbe9e904e…93bf
0x34b655…2a6f
6 touches
3 conflicts
0x350c7a71…8d82
0x34b655…2a6f
4 touches
1 conflict
0x3b806b7a…3c51
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x8f4c5cb2…cbee
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity