← previous blocknext block →recent activity
Analyzing
Block #83,951,730
24 transactions · 21 stateful · 2026-06-27 03:32:33 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,951,730 · 24 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
2w03w04w07w19w110w213w014w115w216w318w320w423w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xa72fd366…c5f8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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