← previous blocknext block →recent activity
Analyzing
Block #81,835,024
30 transactions · 25 stateful · 2026-06-17 07:58:25 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,835,024 · 30 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
1w02w13w24w35w07w38w39w411w012w114w115w016w117w218w419w525w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity