← previous blocknext block →recent activity
Analyzing
Block #83,410,399
19 transactions · 15 stateful · 2026-06-24 15:20:47 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,410,399 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w010w111w212w117w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967b4a40…7a78
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x3abe485c…4073
0xd32edf…ff58
5 touches
3 conflicts
0x3966c94d…44f5
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
3 conflicts on slot 0x967b4a40a6…d67a78
Audit this contract →
← previous block·next block →recent activity