← previous blocknext block →recent activity
Analyzing
Block #84,573,314
12 transactions · 11 stateful · 2026-06-30 00:35:05 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,573,314 · 12 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
1w04w05w18w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6836671…5c3c
0x34b655…2a6f
5 touches
3 conflicts
0xdedae2fd…d091
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x6422fec5…2d86
0x34b655…2a6f
4 touches
1 conflict
0xa4994f59…060c
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xb683667184…055c3c
Audit this contract →
← previous block·next block →recent activity