← previous blocknext block →recent activity
Analyzing
Block #83,874,917
23 transactions · 23 stateful · 2026-06-26 19:00:34 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,874,917 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w112w513w614w517w219w421w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0x545c2ef2…7441
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0xdb95e18e…c737
0x1b6862…e19c
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity