← previous blocknext block →recent activity
Analyzing
Block #83,638,477
22 transactions · 17 stateful · 2026-06-25 16:43:01 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,638,477 · 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
1w03w18w09w110w011w112w214w219w020w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8a49b87…5d96
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x288123d4…728c
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x67d8619b…dcd7
0x34b655…2a6f
4 touches
1 conflict
0x71a8417d…9ae4
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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
10 conflicts on slot 0xd8a49b878e…045d96
Audit this contract →
← previous block·next block →recent activity