← previous blocknext block →recent activity
Analyzing
Block #83,635,794
12 transactions · 11 stateful · 2026-06-25 16:25:04 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,635,794 · 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
3w04w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x672fd8ba…9e9e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x95cb8e34…5eba
0x34b655…2a6f
4 touches
1 conflict
0x6767aeb1…eabc
0x34b655…2a6f
2 touches
0 conflicts
0x785889c9…0603
0x34b655…2a6f
2 touches
0 conflicts
0xb817c8f4…0a13
0x34b655…2a6f
2 touches
0 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
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
1 conflict on slot 0x672fd8ba57…cf9e9e
Audit this contract →
← previous block·next block →recent activity