← previous blocknext block →recent activity
Analyzing
Block #83,496,270
13 transactions · 12 stateful · 2026-06-25 00:53:57 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,496,270 · 13 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
6w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xec8f9288…5615
0x34b655…2a6f
4 touches
1 conflict
0x09a4820b…2db8
0x34b655…2a6f
4 touches
1 conflict
0x0ddc1219…17b7
0x065c9d…c394
2 touches
0 conflicts
0xec938aa9…cb15
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0xb99958f6c8…c6ccf0
Audit this contract →
← previous block·next block →recent activity