← previous blocknext block →recent activity
Analyzing
Block #83,653,865
12 transactions · 10 stateful · 2026-06-25 18:25:44 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,653,865 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705f195d…cc32
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0xe4904797…af04
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x1622fb10…53cc
0x34b655…2a6f
4 touches
1 conflict
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
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
3 conflicts on slot 0x705f195df0…e4cc32
Audit this contract →
← previous block·next block →recent activity