← previous blocknext block →recent activity
Analyzing
Block #83,411,733
18 transactions · 17 stateful · 2026-06-24 15:29:40 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,411,733 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w17w28w310w411w012w516w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x967b4a40…7a78
0x34b655…2a6f
10 touches
10 conflicts
0x4efb974a…6126
0x34b655…2a6f
8 touches
6 conflicts
0x5d2b5661…df66
0x34b655…2a6f
6 touches
3 conflicts
0x5f91ee13…5aef
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x4a1c0d58…9cff
0x34b655…2a6f
6 touches
3 conflicts
0x51b982be…0de2
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity