← previous blocknext block →recent activity
Analyzing
Block #78,942,763
28 transactions · 20 stateful · 2026-06-03 22:23:53 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #78,942,763 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w215w320w023w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x1bc66ca2…fb4e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x1f8a126c…9aa6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity