← previous blocknext block →recent activity
Analyzing
Block #83,853,954
15 transactions · 13 stateful · 2026-06-26 16:40:43 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,853,954 · 15 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
1w04w06w08w110w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4b86ec…900f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0x7c5260f4…bd96
0xa6afd3…d132
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0xa975771f…cbda
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
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 0xea4b86ec74…1a900f
Audit this contract →
← previous block·next block →recent activity