← previous blocknext block →recent activity
Analyzing
Block #83,631,728
13 transactions · 12 stateful · 2026-06-25 15:57:53 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,631,728 · 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
1w02w14w06w17w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x32229dd3…4dbb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6e316d86…5710
0x065c9d…c394
2 touches
0 conflicts
0xb0771a20…62a8
0x065c9d…c394
2 touches
0 conflicts
0xcd9a9bc6…b25f
0x065c9d…c394
2 touches
0 conflicts
0xfb41a7f4…bbb8
0x065c9d…c394
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
3 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity