← previous blocknext block →recent activity
Analyzing
Block #83,628,352
12 transactions · 11 stateful · 2026-06-25 15:35:21 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,628,352 · 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
1w02w14w06w18w29w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a5dd7b4…fba4
0x34b655…2a6f
6 touches
3 conflicts
0xd7add284…8d28
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd203f511…d522
0x40c49f…2af0
3 touches
1 conflict
0x1b9b037a…8286
0x40c49f…2af0
3 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
3 conflicts on slot 0x5a5dd7b4d7…36fba4
Audit this contract →
← previous block·next block →recent activity