← previous blocknext block →recent activity
Analyzing
Block #83,636,513
18 transactions · 17 stateful · 2026-06-25 16:29:53 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,636,513 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w17w28w313w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x672fd8ba…9e9e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd5d0a749…c426
0x34b655…2a6f
6 touches
3 conflicts
0x8ad0ae9d…a19f
0x34b655…2a6f
6 touches
3 conflicts
0xc865e86b…8693
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity