← previous blocknext block →recent activity
Analyzing
Block #83,632,348
14 transactions · 11 stateful · 2026-06-25 16:02:02 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,632,348 · 14 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
2w03w14w08w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6984da…21e5
0x34b655…2a6f
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x23bcb6e8…566e
0x34b655…2a6f
4 touches
1 conflict
0x287e0819…37b5
0x34b655…2a6f
4 touches
1 conflict
0x2edd9789…38be
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x3ae6b00e…d4c5
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
3 conflicts on slot 0x7c6984da0c…7821e5
Audit this contract →
← previous block·next block →recent activity