← previous blocknext block →recent activity
Analyzing
Block #83,495,282
10 transactions · 9 stateful · 2026-06-25 00:47:22 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,495,282 · 10 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
1w03w14w07w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9fe0433…7f01
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0xa592dff2…81a4
0x34b655…2a6f
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0xc9fe0433ca…417f01
Audit this contract →
← previous block·next block →recent activity