← previous blocknext block →recent activity
Analyzing
Block #83,400,243
18 transactions · 17 stateful · 2026-06-24 14:12:54 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,400,243 · 18 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
1w02w13w24w35w48w513w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe155a04c…f267
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xdb13034e…be94
0x34b655…2a6f
8 touches
6 conflicts
0xdf37a93d…879b
0x34b655…2a6f
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
10 conflicts on slot 0xe155a04cc1…f3f267
Audit this contract →
← previous block·next block →recent activity