← previous blocknext block →recent activity
Analyzing
Block #83,625,440
30 transactions · 24 stateful · 2026-06-25 15:15:51 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,625,440 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w26w17w011w112w113w014w115w216w320w022w424w226w127w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8190162b…5c4b
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x65bd5770…5ecd
0x1b6862…e19c
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