← previous blocknext block →recent activity
Analyzing
Block #83,654,965
24 transactions · 17 stateful · 2026-06-25 18:33:01 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,654,965 · 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
1w02w14w28w014w115w217w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b7c45d…9d5a
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x74b52a70…e2f4
0x34b655…2a6f
4 touches
1 conflict
0x8dd1a323…8080
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xb6b7c45de7…c49d5a
Audit this contract →
← previous block·next block →recent activity