← previous blocknext block →recent activity
Analyzing
Block #83,654,341
13 transactions · 13 stateful · 2026-06-25 18:28:54 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,654,341 · 13 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
8 touches
6 conflicts
0x5bd818fc…4f86
0x34b655…2a6f
8 touches
6 conflicts
0x72f83c64…2e54
0x34b655…2a6f
6 touches
3 conflicts
0x89f2822c…00da
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9f715341…353a
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xbf582a3e…ca85
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 0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block·next block →recent activity