← previous blocknext block →recent activity
Analyzing
Block #83,623,528
12 transactions · 11 stateful · 2026-06-25 15:03:08 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,623,528 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43fabcc3…2df4
0x34b655…2a6f
4 touches
1 conflict
0x4ed3af20…d87d
0x34b655…2a6f
4 touches
1 conflict
0xc212dabd…e7b5
0x34b655…2a6f
4 touches
1 conflict
0xc2ab3ad1…a6bc
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
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
1 conflict on slot 0x43fabcc30a…ce2df4
Audit this contract →
← previous block·next block →recent activity