← previous blocknext block →recent activity
Analyzing
Block #73,696,593
22 transactions · 18 stateful · 2026-05-10 15:05:27 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,696,593 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w010w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x7ee110ef…8394
0x34b655…2a6f
10 touches
10 conflicts
0x50c2960c…5f37
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x00f245ce…1e10
0x34b655…2a6f
8 touches
6 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0x22863bf9…19df
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity