← previous blocknext block →recent activity
Analyzing
Block #83,671,197
15 transactions · 15 stateful · 2026-06-25 20:21:16 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,671,197 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x99ee776a…053a
0x34b655…2a6f
6 touches
3 conflicts
0x913ebf0e…d816
0x34b655…2a6f
5 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3863eb34…c4e5
0x34b655…2a6f
4 touches
1 conflict
0x3deac4a2…d2bd
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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
6 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity